stormbeta

Why would you think about whether it was relevant in 5 years? I've literally never cared or thought about that when sending those kinds of messages. It's just a basic picture, not sexting or something else potentially sensitive.

I don't understand why I should force everyone I know to install yet another random social media app when a regular message works just fine.

>You can post pretty shamelessly the little things you're up to all day to your story, knowing it will be gone in 24 hours, keeping your feed really clean.

This is the part I still don't get. Why would I want to constantly spam my friends with trivial photos of my daily life? Disappearing spam is still spam.

I'm 28, nobody I know uses snapchat/instagram/whatever so I haven't actually used it. If it's something I actually want to share, I don't care if it's gone in 24 hours and it's dead simple to just message them directly.

The article doesn't appear to be blaming Javascript as a language, but rather the Node.js ecosystem as a server platform.

Not all tools are appropriate for all niches. The author made it clear they don't have an issue with Javascript as a whole or even with Node.js necessarily, but rather the use of Node.js as a major server platform or as a platform for large applications.

Personally I don't understand the hype around smartwatches in general.

Don't get me wrong, I understand them as a viable product and why a lot of people like them, but the demand for them was wildly overblown.

Of everyone I know, only one or two people have one, and it's not because of price. If you're a huge fitness nut, deal with an enormous number of messages, or just plain like the gimmick, they're great. But otherwise they really don't offer much that offsets the cost, need to charge the things on a daily basis, and general hassle of having yet another electronic device to keep track of.

I agree about JSON, but I can't say I understand the logic behind TOML.

I know it's supposed to be a config format, but it only seems to make any sense for INI-like configs that are little more than a flat key-value map.

The places I see people using JSON/YAML/etc for config are much more likely to have nested structures that would be extremely awkward to represent in TOML. I think YAML was on the right track, and if you ignore the messier parts of the spec it works pretty well.

JSON is an interchange format, but YAML is pretty obviously meant for configuration, given the huge emphasis on human readability and editing.

As for TOML, it's a good replacement for mostly-flat INI-style files but the syntax is really awkward for the kinds of places you'd normally use YAML, especially nesting lists/maps.

Agreed. Even beyond the monetary aspect, it'd be an absolute headache to have to replace this stuff with any frequency.

The biggest reason I'm a skeptic though is the incredibly carefree and reckless approach I've seen used by many IoT devices.

The Nest is a great example - I was shocked to discover there's no division between the part that directly controls the furnace/AC/etc and the rest of the device. That should've been a no-brainer, because first and foremost the device shouldn't cause harm, and when the "smart" portion inevitably has a problem (even if temporary), a user shouldn't wake up to a frozen or overheating home.

This stuff needs a higher level of safety and guarantee, and treating them like smartphone apps is going to end very poorly.

Jenkins + generated jobs (i.e. jenkins-job-dsl or the new Pipeline DSL), and keep as much as the build configuration and logic in your project where it belongs. The configuration that lives on the CI server should be pretty minimal.

We have a custom wrapper around the jenkins-job-dsl that encodes our conventions and templates to generate several hundred jobs, and it works very well for our medium-scale instance.

SwiftKey on Android is still by far the best for me, but unfortunately other problems with Android (namely the dearth of high-end devices under 5") are probably going to force me to switch to iPhone.

The default Apple keyboard makes me incredibly frustrated, especially when used one-handed (which is 90% of my usage). No flow typing, and nearly all numbers, punctuation, and symbols are locked away behind layers of menus. I do find it the most accurate for typing in unpredictable plain text, but that's not very useful even for passwords (LastPass + most of my passwords have symbols in them).

Most of the third party keyboards are crippled shadows of their Android counterparts, but I can least get flow typing through them.

For starters, any utilities based on sourcing won't work, such as nvm/rbenv/etc.

That's technically true for zsh in cases, but it's far easier to port or add compatibility for zsh than fish.

Personally I prefer uMatrix - it lets you enable specific things across domains instead of a binary allow/deny, and allows global versus per-domain or per-subdomain rules; e.g. I might be fine with one site collecting metrics but not globally.

You get a similar effect for free with any language whose community defaults to non-floating transitive dependencies, e.g most JVM languages.

I have CMD+arrow keys for that, and those key combinations are often easier to reach that home/end/pgdn/pgup on many keyboards.

Haven't really needed a separate delete/backspace key. About the only time I use the separate delete key even on windows/linux is in the file explorer.

There's a psychological difference between knowing it in the abstract and actually being confronted with and able to play back that history.

And least for this, there's a way to delete it.

I couldn't disagree more. There should always be a way to make the content I'm looking at bigger in order to see it more clearly, especially for users with poor eyesight.

"responsive design" does not magically eliminate this need, and I agree with the posters saying that disabling of user-scrolling should never have even been allowed in the first place.

And that's not even touching on the fact that most "responsive" sites I've seen get it horribly wrong.

It's still a massive issue for me. My Z3C is the first smartphone I've ever owned that pretty much always makes it through a day, even days with heavy usage and I'm stuck trying to make a call at 2AM.

Most smartphones would crap out anywhere from noon to 6-7pm - and my usage isn't that heavy on typical days, maybe 1-2 hours of screen on tops and an hour or two of bluetooth audio.

Sure, I'm often around sources of power, but that means I now have to carry cables, chargers, and battery packs around as part of my daily routine or when going hiking and biking. No thanks. With my Z3C, I no longer have to carry all that junk around, and I know I'll still be able to use it in an emergency even if I get stranded somewhere.

And even if I carry all that crap around, just because I'm usually around sources of power doesn't mean I'm always around sources of power.

Simple regexes are still fairly readable (e.g. a three number version string match), but if you find yourself having to worry about stuff like matching within escapable delimiters, it's time to put the regexes down and pick a different solution.

This is a big part of why I've been reluctant to buy an iOS device.

Originally it was because of the requirement to use the first-party keyboard software, but now it's because they've changed the design language in a way that conflicts with everything but iOS - and as a result, the UI feels remarkably unintuitive and confusing, even if it makes sense internally.

Too bad most of the community there is made up of the worst of reddit. Maybe if enough normal users moved there it'd be worth it, and maybe that will actually happen if reddit doesn't figure out how to salvage this, but until then, there's nothing on voat worth wading through the sewage.

Honestly, I wouldn't even be mad if that was actually intentional. Reddit's community in the larger subs has been getting really awful of late.

No kidding. I really thought Hacker News was better than this, but a large number of the replies here are little more than parroted MRA talking points and other myopic comments.

I've been seriously considering switching to a Kobo. I already convert/strip the DRM from all my books anyways, as I loathe the idea of ever being stuck in one ecosystem (and have switched before, from Kindle -> Nook -> Kindle).

The new waterproof Kobo especially shows me that Kobo actually understands making a better e-reader.

No offense, but where on earth did you get that impression from? I have a feeling whoever told you that has either never used npm with a non-trivial project or was messing with you.

I've had more issues with npm in the last month than I've had with pip, gem, and apt combined over the last two years. "most unreliable package manager" is an apt descriptor.

The private registry is easy to get running, but actually using it is very, very clunky.

I understand they want the public index to "always work", but the requirement to tag images with FQDN for docker to even try to use a separate registry breaks a lot of a very common use cases, such as transparent caching and mirroring of images.

Keep in mind the request count too - lots of small packets can be considerably slower than their net size would suggest, especially if one gets dropped.

I assumed mistercow was talking about things like drawn erotica, not actual CP.

As far as I can tell, no one's sure yet.

True, but you're still talking about people who felt it was important to leave a review. I try to leave reviews of everything I buy, but I frequently forget to do so if the product performs as expected (neither exceptionally good nor bad).

Doesn't appear to work in Chromium under Xubuntu 12.04, despite the message about it working best in Webkit. Works fine in Firefox though.

But no middle click, which is something that the ThinkPads have and something I use every day. I also prefer the track point nub, as it lets me keep my fingers on home row.