HN user

hello_there

90 karma
Posts2
Comments48
View on HN

This looks like a very nice product and it matches exactly something that I've been wanting and thinking about. So I tried to order one (using PayPal), but it doesn't seem like you're shipping to Norway. Are you planning to open up for shipments to more countries any time soon?

I clicked through to the tiling WM that he was using for KDE and one of the things under "Features" that got my attention was this:

Support for setting windows to floating or quitting tiling altogether, per-desktop (Meta+Shift+F11) and per-window (Meta-f) (“Meta” refers to the “super” or “windows” key here)

I think this might be worth a try...

If you find this interesting then you might also be interested in SnapRAID: https://www.snapraid.it/

SnapRAID is a backup program for disk arrays. It stores parity information of your data and it recovers from up to six disk failures.

SnapRAID is mainly targeted for a home media center, with a lot of big files that rarely change.

If the failed disks are too many to allow a recovery, you lose the data only on the failed disks. All the data in the other disks is safe.

I'm not affiliated with any of the projects.

multi-touch gestures added in Gnome 40

This sounds like a great improvement! Is this Gnome-specific or can we soon expect to see this in other DEs as well?

This looks very nice! I've been thinking about something like this for quite a while. May I suggest two additional features that I would love to see in such a window manager:

1. A way to neatly arrange all the windows on a virtual sphere that surrounds the user, possibly arranging them automatically in a similar manner as a tiling window manager.

2. A way to rotate the before-mentioned sphere around you without forcing the user to rotate it's head. This would avoid much of the neck strain. It could be done by, for example, holding a button on the keyboard while moving the mouse or by a simple keyboard shortcut to rotate the sphere by X degrees in any direction.

This concept could also be extended to virtual desktops where each desktop is a sphere around the next, like an onion, with the ability to "zoom" in to the next desktop.

Imagine you know someone in the public eye, let's say a musician, with their own website. They enable comments

In my mind it would be the users, not the site owners that would enable the comments.

People are posting a high amount of offensive content. What do you advise that this musician does?

My advice in this case would be to create a moderator stream that the end users can subscribe to. Perhaps some mechanisms could be put into the system to make it easy for site owners to suggest a "default" moderation stream that the end-users can opt-in to.

In this case the site owners would be able to moderate comments through voluntary cooperation with its users, but it wouldn't be able to censor opinions that it didn't agree with, because the end users would always be in control of how its stream is filtered and would always be able to verify that on-topic posts aren't censored.

I haven't thought out the details, but I really think that it should not be the website owner, or any other individual or organization, but rather some sort of decentralized community effort. For example, one could imagine a distributed log that every commenter and moderator appends to and that is replicated to different parts of the world -- each of which a client could subscribe to.

Here's a slightly off-topic dream about online comments:

In an ideal comment system I believe that articles, comments and moderation events should come from three different, decentralized streams (like Atom) that the end user can subscribe to individually and that are joined at the end users client. That would would provide transparency to the moderation process, ability to comment anywhere, and it would allow moderators to become effective spam-filters without giving them the power of censorship. Now, imagine if this system was built into the browser and it became the default commenting platform for all websites...

when stdlib will be more @nogc friendly

How does @nogc work in D? Is it easy to keep track of what needs freeing and what does not or is it easy to mix up and get hard bugs? Also, what do these bugs look like? Is use-after-free possible or how is the failure mode i that case? Is it possible to call free on an object after it's been garbage collected?

FLAVOR: Ubuntu Desktop

HEADLINE: Ability to completely disable all dpi scaling

DESCRIPTION: I've bought a high-res screen with the intention to get more screen real-estate, but it seems that every modern app is working against me by scaling up the GUI. I wish this could all be easily disabled in one place.

Flynn 1.0 is here 10 years ago

I would really like to see an article comparing Flynn with Deis. Last time I looked it seemed to me like two different implementations of the same thing. What are the differences?

I would imagine that Command & Conquer-like games could be a good fit for VR as it requires overview where you'll usually have to scroll in cases where you'd otherwise just lift and eyebrow.

I could also imagine a Window Manager where every window is placed in a large (huge) sphere that surrounds you and your chair (you are stationary in the middle). You could turn you head to see and interact with windows that are nearby or you could zoom out and rotate the whole sphere by using some shortcut or other device (maybe an ergonomic mouse with a ball on top of it [1], such that the sphere around you rotates in the same direction as the ball of the mouse). You could still map virtual desktops to a zone on the sphere (or perhaps just create virtual spheres). With some handy keyboard shortcuts I could imagine this to became quite awesome. Especially for programmers that use many windows at the same time.

1: http://www.ergodirect.com/images/Logitech/16728/large/Logite...

Cool stuff. I really like the idea, but why so many symbols? On slide "2.5 Piping" I find the description on the right to be far more readable than the examples on the left. Also the descriptions on the right are familiar, idiomatic Scala which is also a plus. The stuff on the left is impossible to decipher without some documentation and I don't see how it adds value except from saving a few chars. OTOH it introduces significant load on the developer that has to look them up (again and again) in the manual. If saving these chars are important then one might defend introducing a single new operator for some well thought-out abstraction, but introducing 7 new operators is just to much for anyone to remember. Especially the two last operators seems entirely redundant as the language already has quite compact syntax for function invocation (as does any language).

Atom 1.0 11 years ago

I'm running Atom 0.116.0 on Xubuntu and AltGr works perfectly fine. My keyboard layout is Norwegian.

I find it interesting that Java didn't become the standard for this as it seems like it has everything and is both fast and mature.

What might be the reason?

Great. I've been wanting something like this for a while. I've got a few questions:

1. How large files are supported?

2. It says that it will only persist primitive fields on objects - does that exclude persisting a byte array?

3. What are the failure semantics? For example, what happens if my computer's power supply fails in the middle of a write? How will the program behave the next time it is started?