skysight-inc/HackerNews huggingface dataset:
> Don't upgrade your phone. Seriously.

The market makes this easy nowadays. Unless your phone is broken/severely outdated there is next to zero benefit to upgrading at this time. Prices for flagships become prohibitive as well.

Upgrading phones every 1-2 years is a dead tradition outside of contract incentives, only relevant to hyper enthusiasts (r/android etc...). Even then I am not sure why aside from corporation benefits. The differences are marginal at best (ok, Candy Crush 4D gets 8fps more nowadays), the value of upgrading has declined for years now.

Of course these statement will have enthusiasts screaming and foaming because the newest FiveMinus 8T has 1mm less bezel while sporting 25 mAh more battery compared to last years model. Also NIGHT VISION CAMERA! All the not-quite photography-enthusiasts are salivating and throwing their money at phone makers year after year in order to participate in blog-jerk-offing and karma whoring.

People who care about photography get DSLRs, people who care about functional functions in phones haven't had to react to significant changes for several generations now, unless lack of security updates (cough Google) forced people to. WhatsApp, Instagram, Firefox, Mail, Dial, Weather, Auth Apps, ToDo, ... they all run fine on still supported iPhone 5S/SE or older supported Androids. What app that an iPhone 5S cannot run is even truly useful and missed?
Southwest didn't buy the option either until after the Lion Air crash:

In manuals that Boeing gave to Southwest Airlines — the biggest operator of both the MAX and 737s in general — the warning light was depicted as a standard feature just as it is on older 737s, according to Southwest spokeswoman Brandy King.

After the Lion Air crash, Ms King said, Boeing notified Southwest that it had discovered the lights did not work without the optional angle-of-attack indicators, so Southwest began adding the optional feature too.

(quotes from https://www.abc.net.au/news/2019-05-06/boeing-knew-737-probl... )
> BTRFS has no future

This is FUD.

Btrfs is actively developed and its problems and limitations are acknowledged by upstream in an honest way. Many people DO use it with no more problems than they have with XFS or OpenZFS.

The only people who say "Btrfs is dead" are those who don't use it. It's a bit like people who snigger at the whole "Perl looks like line noise" trope without ever having writting a line of Perl in their lives.

In every report that I have seen of Btrfs doing something bad is when somebody (myself included) has done something incorrectly, not read the docs, not consulted an expert before doing something complicated, not taken the time to understand how it works, using a suboptimal or flakey hardware/software stack underlying it.

Have you seen how strict the FreeNAS community is about using proper, server-grade hardware and configuring the system properly to prevent data loss? This is a very good line to stick to.

Unfortunately Btrfs doesn't have the same consistent message but if it did then there would be fewer problems.

I regularly use Btrfs at home and so far I haven't had any problems. I would not use it in production when other people's data is on it YET.

One reason is technical, and it's too much of a cognitive burden these days when combined with other people's data.

The other reason is because of customer expectations, i.e., because of FUD that people like you are spreading. If there was some data loss, the customer would be angry at me for choosing Btrfs because "everybody knows" that it's unstable /s. If I am using ZFS then there's less of a chance that customers think I make bad decisions and there is a small chance they will be more forgiving.

Mdadm + LVM + XFS is an excellent alternative. The only reason that I don't use this more often is because snapshotting requires twice as much disk space as you plan to use. Otherwise I probably would be using this stack exclusively.

Getting back to the original "Btrfs has no future" nonsense, the only reason this is true is if people make it true. Therefore, one important reason I use Btrfs is that I want to see it succeed. That can only happen when people actually use it and advocate for it in a positive and honest way.
Seems actively developed indeed: [1]. The current contributors are Facebook, Fujitsu, SUSE, and Oracle.

Its XFS which never had a future because it lacks features which modern filesystems have. Adding these features would be akin to making a new filesystem (which could contain the acronym XFS).

The only real (integrity) issue BTRFS currently has is write hole in RAID5/6. Its a long standing issue...

[1] https://btrfs.wiki.kernel.org/index.php/Contributors
The title should mention this, then. WebGL and WebGL2 aren't the same thing.
Im afraid nothing will change to the moment people start dying because of climate change effects. And by that i mean at leadt hundreds of ppl of not thousends.

Fastest move would happen if what im talking about did happen in 1st world countries.

Thats sad masses need such a strong shake up.
You expect the meeting to be held in the middle of the night? 'The meeting is today at 2!' is unambiguous in most cases (certainly with a 9-to-5 job).

In many locales where the 24 hour clock is used, people refer to the hours after noon as one, two, three o'clock etc. Then when you write it down somewhere two o'clock becomes 14:00.

OP's pet peeve is kind of weird though. Even with a 24 hour clock writing 9:00 for 'nine in the morning' without the leading zero is quite common, if not prevalent.
It's not so much that there aren't enough individuals that are committed to change. I think it's partly that people would rather do than be done unto (the feeling of controlling your destiny rather than being controlled), and partly that people can be gamed to act against their own long term interest (ironically being controlled into thinking you're in control when you aren't).
Please don't post flamebait like this again. It's flamebait because it's both inflammatory and unsubstantive. It's like spending your last dollar to buy spoiled milk.

https://news.ycombinator.com/newsguidelines.html
The biggest temporal fail of the web is date. For some topics, it’s impossible to tell whether the author was working in 2012 or 2019.
There is; I work with teams / partners in the US/EU/AU. Ofcourse I can just check the person who writes it and jump to their time frame, but why not just say 14:00 and preferably a timezone.
If "no classes" can be considered "where it shines", it seems to me that the bar is not very high.
So far yes, but it's an open house.
I use am/pm because that's how I was taught to tell time growing up, and in my corner of the world (northeast US) nearly everyone uses it. "2 pm" is immediately meaningful to me, but to parse "14:00" I have to subtract 12 in my head. Even when the am/pm is left off, it's usually clear from context.

I'm not arguing for the inherent superiority of am/pm notation, but I do get frustrated with people who use 24-hour time because "it's more logical", without seeming to realize that it's more difficult for the majority of people to understand.
I can relate. These days I think any feature request should be followed by a discussion about what the client/user is actually trying to achieve. It's my experience that most users, unsurprisingly, have no idea about the possibilities and limitations of the apps/services they work with and will limit their imagination to the tools they already know - whether it's the the idea of faster horses as mentioned by Henry Ford or the tables from your story.
I don't get this. $1000 is not a lot of money if you spread it over 2 years or even 5 years. I still use a 5 year old flagship. In other words it can be the sensible choice if you're willing to plan ahead, compared to just buying the cheapest stuff you can find and then throw it away after it breaks due to the lower quality. My micro USB port is wearing out and it is difficult to charge the phone. I will most likely have to get a new one in 2019. Features like wireless charging or waterproofing that would extend the life of my phone are mostly only available to flagships. On top of these benefits you also simply get a better phone.

So now suddenly a company screws over people and it affects poor people disproportionately. Of course it's the fault of those poor people because they failed to plan their finances correctly and shouldn't have bought an expensive phone. Except they can afford the advertised plan and perhaps they even have chosen a phone according to the points I mentioned above because it will save them money in the long run.
So why are we blaming the customers and defending the company's disgusting behavior? Do you really think it should be normal that companies are screwing you and it should be the responsibility of the customer to defend himself against what basically amounts to fraud?
I mainly use Python but that would still be unclear to me.

I think the ternary operator is the sweet spot between too verbose and too confusing.
The multi-line comparators are definitely clearer and more readable to me.

The 10(!) lines of code you referenced are actually only 8(!) lines compared to your 1(!) line because you included the function declaration and the final brace in your count. The line you proposed is 34(!!) characters wide. I wonder if your statement will continue to grow past 80(!!!) characters as your operand expressions grow in width? Will you transform it back to multi-line when that happens?

However, I'm not sure why we're exclaiming line counts at all and now, apparently, character counts.

Agreed on the semi-colons though.
It very much is, and those who live in those regions have no idea that it is.
Currently no.

Intel has dropped MPX support from newer generations, given that their design was buggy and no one bothered to actually make use of it.

So they decided that improving the design wasn't worthwhile.
There's a thumbnail index for MagicPoint slides: https://www.openbsd.org/papers/ru13-deraadt/index.html

I also highly recommend checking OpenBSD's events page for additional slides/papers and videos.

https://www.openbsd.org/events.html
The Twelve Days of Safety Myths
You should be consciously aware of who might emergency contact you anyways. Add them to your whitelist.

Edit: all good points. Yeah I guess that is a risk.

Also reminds me of this:

https://youtu.be/J-inCB3POqs
The fact that this is considered a possibility is abhorrent and should be addressed immediately. As a society how can one accept such realities as normal but at the same time condemn other countries that have gulags and prison work camps?
Ha! Your story fits neatly within the self-determination theory of motivation [1]. You clearly tweaked your autonomy to be higher.

I'm a big fan of the theory, but I almost never see clear cut examples like this in the wild.

[1] https://en.wikipedia.org/wiki/Self-determination_theory
I find that odd. Even over a 14.4 modem (which was obsolete by that time) it would only take about 5 minutes.
That's maybe mostly a semantic quibble about the precise meaning of trust. I don't think it's considered absurd to say "I trust that my plane won't crash" when flying. Maybe it's more usual to say "I hope that my plane won't crash". It appears to be the case that we "hope" if we don't see the social dimension of the phenomenon we are referring to, while "trust" is also communicates a stronger social dimension.

Note also that in interactions with humans, we generally don't have a precise probabilities.
I think you can reject impossible derivatives, though only if being very fucking careful.
Would widespread use of synthetic meat solve the antibiotics issue (as well as help with global warming)? I have only researched synthetic meat a little bit and am wondering if anyone has more concrete information and opinions.
CEO of WAX and Opskins explains gaming today in cool podcast recording
heh, that would never have happened on my lineage smart brick, were the alarm app just goes to sleep as well. Certainly a most non-invasive app..

But yeah, this seems to be a bad design decision.

Let us meet in 4 hours in a different time zone doesn't seem to be a likely scenario. And even then it wouldn't make that much sense.
I started a First Team at our son's school. It was challenging. Raising the money to buy the kits and equipment was the easiest part despite our school board not having anything budgeted to it. Beyond myself, we could not get any of the other parents to commit any time to it. So we struggled and eventually collapsed. The other parents were treating it as a free afterschool program. 20 kids, 3 volunteers (1 parent, 2 teachers) and not a lot of time to teach FLL and programming concepts.
I came very close to missing a flight because of this too. It's ridiculous.
That's the rub.

Let's plan a theoretical test case. At a minimum, you'd need two maintenance guys, maybe one and a pair of tools. One guy to tweak the sensor outside (as several hundred mile per hour airstreams aren't exactly in plentiful supply, or easy and trivial to reconfigure in a hangar near you), and a guy in the cockpit, reading off the measurement on the computer against some sort of calibration chart.

The "tweaking" part would probably be done with some sort of precision test mount (that I doubt they even build into the plane.)

Also, odds are, you'd only detect very specific types of disagrees on the ground. Bad springs should be trivially deducible from the forces required to create measurable deflections.

Bad potentiometer connections should be deduceable from checking output voltage against the component spec sheet while deflecting.

Unfortunately, this dive into Electrical Engineering won't stop until you've taken into account every length of wire and eventually, every circuit board and line of code between that sensor and the avionics suite. If some FOD for instance, was slowly wearing through the wiring and insulation leading from the sensor to the computer, or an inductive cross-talk event occurred, or something shorted. Etc, etc.

And all of this work and diagnostics would need to be done by someone whose documentation told them the AoA sensor was a non-critical component so the manufacturer could cut corners.

Oh yes.
<double facepalm>
Been here before.
Way.
Too.
Many.
Times.

Not in safety critical systems , mind, but oh the web's I've seen woven.
> This is not really a tenable suggestion either unless you are suggesting everyone take a giant hit to yield

Some believe divestment won't have significant impact on returns:
http://www.lse.ac.uk/GranthamInstitute/news/the-mythical-per...
I wasn't defining "broken" as "the engineers find it distasteful". I was defining it as "broken".

I agree with this:

> 6 months to deliver 2 applications that each work 80% often provides more business value than 6 months to provide one application that works 100%.

Though this is a question of product management prioritisation, not engineering practice. "It's faster to not write tests" depends entirely on a definition of completion that ignores the cost of repairing defects and coping with faults and failures in production.
> majority of people to understand.

Depends where / with who you work? Most of my colleagues have to think the same way about am / pm and often get it wrong when it's 12:00 am/pm.

The 'it's more logical' for me does apply there; in the 24:00 you cannot get 12:00 or 00:00 wrong no matter how you think about it. It feels intuitive in every way.

12 hour clocks made sense when clocks had 12 hours on them; then you had to somehow indicate which block of 12 hours; that problem was fixed before I (and probably you) were born though.
I find your example to be on the clever spectrum.

If anything, it should remind you that clarity depends on the context.
This is very common in the web agency world, where budgets and hourly rates intersect at a place where there's hardly enough time to build out features. Testing is seen as eating up time that could be better used getting through the backlog.
Go straight for Kelvin
Not without writing that 10-page rant....
I believe the parent is taking about an emergency where the hospital calls, not the person.
The problem with individual action is that it requires a collective effort to make such sacrifices worth it, and most people aren’t willing able to make all or any of those sacrifices.

For example: one cannot simply replace air travel with trains in the US. Amtrak is wholly inadequate to act in an interstate commuter transport capacity in the vast majority of the US.

Also, I’m not at a point in my career where I can afford to work part time. Part time software engineering jobs are hard to find in the US, and part time jobs don’t provide benefits like healthcare.

Individuals are going to look at this and say “why should I make these sacrifices when I know that others aren’t going to make them?”
After using btrfs a couple of times and I don't think it's a good idea to call it stable yet. I expect a stable filesystem to perform well and work without admin intervention, both of which btrfs has let me down on.
Unrecoverable is a bit much, but it's a pain.

There are of course environments where XFS is fine but it's failure cases are pretty bad. I accidentally (wasn't paying attention) used XFS at home once on a NUC that was my UniFi controller and Pi-Hole; any time it lost power it'd hose the partition and make it unmountable. I'd have to go find a monitor and a keyboard and boot it single-user to recover.

My fault (we were selling the house and buyers love throwing breakers) but still not awesome. I run boot drives as ext4 exclusively now and I definitely pay more attention during setup.
What you say is true, but I'm not sure it's in contradiction with my point.
This is exactly the same defence people have about the imperial system. (I'm british so have the 'benefit' of having both systems existing in my head as a weird mish-mash).

I can take it as a "con" against any new system, but it doesn't outweigh all other benefits- if it did then there'd be no progression in society -ever-
That's not really feasible. You might know for which persons you are the emergency contact but you can't possibly know from which phone you would be contacted in case of an actual emergency.
Lying to immigration officers is a crime. If you're going to go that route, you better be damn sure it's gonna work and they don't have prior information on you.

If you're at the point where this seems like a good idea, you're better off not bringing data over the border.
The logistics of parts is one thing.

Training and certifying mechanics to install them is a separate thing, since you must also prepare sufficient trainers and certifiers. This not an instantaneous process. There are two stocks with dependent flow rates.

Incumbents don't feel this as acutely because they have dealer networks on top of many independent mechanics.
This is potatoes.
Want to rage? Read this: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d77...

Who in their right mind thought YYYY-DD-MM is a good idea.
(It's "smart", recognizes the YYYY part and moves it to the end and interprets as DD-MM-YYYY)

The ISO standard specifically used "-" as the delimiter for the standard date format because no one was using it. And MS had to ruin it.
The best approach seems to be making a date+time either "timezone aware" or "naive" (I got this from python's datetime.)

Naive dates don't have a timezone attached, so of course there's no auto conversion. Aware times do.

Now all you have to do is avoid assuming which your user wants. Especially avoid an interface that makes it look like they have a naive date when they actually have an aware one.

For example, if the appointment is timezone-aware, then write the timezone next to it! So if the user writes 10:00 and you auto-convert that and print 10:00 EST, they at least have a chance to correct it.
...I think it's interesting that WebAssembly moves the "code bloat problem" into focus again, because WebAssembly apps cannot afford to have huge upfront downloads or long installations. They must start in a second or so.

The Tetris example is under 60 kBytes (compressed), and that includes all data as well (there's a sprite/font sheet embedded in the wasm blob). This is in the same general size range as 8-bit BASIC programs.

That means that Zig doesn't need a big runtime to work, similar to C, but unlike C# or Java (or even C++ / Rust, unless you ignore most of the respective standard libraries and restrict yourself to a minimal "embedded-programming" style).

Here's a similar example (shameless plug), a WASM C64 emulator in under 64 KByte download size. This is implemented in C:

https://floooh.github.io/tiny8bit/c64.html

I can (most likely) get to the same result in Zig, but with a much nicer "better C" language (and build system!)

(...of course there's a huge web browser dangling off the WebAssembly blob, but this is mostly runtime components that are not even needed for this type of WASM programs (we really need smaller, more modularized browsers!).
Sometimes. But only sometimes. A clever one liner that is easy to misunderstand when reading it while trying to find a production issue with eyes on you is NOT fun at all. And it isn't worth the two lines it saved.

Less code does not mean less bugs.
Yeah, another pet peeve is not using UTC for everything everywhere in business situations. I have i3wm running with my local time + UTC time in the bottom, so I mail people with 'the meeting is 14:00 UTC'.
From the paper:

Of the 20 ME/CFS patients studied, 5 were severely ill and 15 were moderately affected by their condition
You never know who's going to call from what number. Just yesterday I had a carrier I hired call me from the shipper's landline because the situation was going sideways and there was no cell service.
I am using and have used xfs on many systems, from server to embedded. Xfs is reliable and performs well. Debian support is fine. I wouldn't want to switch to any other file system.
I find myself frustrated by a different way in which the "Future Book" is slow to arrive - specifically, the glacial pace that e-Ink displays are improving. I bought each generation and found them better and better, and yet... every generation seems further apart and slower and slower to finally close in on the ideal: black ink on a white, non-glowing background.

The. Background. Is. Still. Gray. Dammit!

So frustrating - I'm an enthusiast for these (for travel). I love owning physical books, but would happily cull all but my top books (you know, 60-80 linear meters of shelf space) and keep a lot of things on e-books. But only if e-Ink displays can finally get to a white background!
The title is a bit of an oxymoron.

"...portable...for Windows"
Really goofy move, in my opinion. The next big social network, Aerosmith! Well, a lot of people don't like that band, but that's cute.
> I do think we should continue to focus on, explore, and advocate for broader systemic change.

Absolutely agree. It's not either/or. We need both. But hey, it's easier to advocate for systemic change if you lead by example. See e.g. https://www.theguardian.com/environment/2019/apr/26/greta-th...
> Revolut

Note that this only applies for business accounts. Regular users as far as I can tell are unable to access the API.