skysight-inc/HackerNews huggingface dataset:
That's why I keep to UEFI - most of the time the configuration just works, and firmware passes down information about serial console to the OS, iirc.
it is natural selection. this is most famous mechanism of evolution.
In my experience, Kindle Unlimited is crap anyway and in no way or form "unlimited" like e.g. Amazon Music is. Almost everything covered is extremely low quality. And the very few books that are worth reading and eligible are cheap anyway (because they're likely self-published), so you'd save money just buying a couple of those every month. (And you'd even get to keep them!) I'd be intrigued to hear opposing viewpoints.

OTOH if you see that a book is covered by Kindle Unlimited, that's an indicator that it's probably not that great so that's kind of useful when you're looking for something to read. :)
There are always many bonehead bills on state legislatures and plenty of seats that run unopposed which go to whoever wants it. They’re generally not worth any attention.
It makes sense but I think there are other factors preventing Linux going head to head with Apple, even with the same quality build. There are apps. I was a long-time Linux user also (and still use it technically), but my main computer is also Apple now.

There are the apps, and even with KDE MacOS is still more consistent-looking than Linux sadly.
Documented population...everyone uses water though
For more details, see Mozilla’s November announcement about MV3 in Firefox 109:

https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signi...
PiEEG Presentation. Raspberry Pi to Measure EEG
You can still break the DRM on books with Adobe DRM (like that used by Google Play books) or Kobo (they have their own DRM but also offer Adobe versions).
> I actually got Cyberpunk 2077 specifically on Stadia so I could play the meta-game of "Can I win Cyberpunk before the unaccountable mega-corpo revokes my access to Cyberpunk?"

> I will be losing that game.

- shadowgovt, https://news.ycombinator.com/item?id=33023050
I don't think you'd be able to support with evidence the argument that copyright has stifled innovation, given that the "modern format" of copyright tracks an extraordinarily innovative period.
As I anticipated, you are referencing research that does not show exact copies being generated by Stable Diffusion. Do "semantically equivalent" images infringe on copyright? I would argue that they do not. We will see how this plays out in court.

Food for thought: if I write instructions for generating an SVG of a black square, does my program contain copyrighted material (Malevich's Black Square)? You and I could argue about that, but you will probably quote more research that disproves your own point. So let's skip that.
I would argue that if they were able to pay down the tech debt that quickly and easily, then most likely the debt wasn’t as bad as described to begin with.
Absolutely that's not just you. This post is childish and absolutely distasteful.
Or just stop trying to force immutability into something that is clearly mutable. You’re only causing unnecessary GC pressure by copying objects.

Never the less this eerily looks similar to Goetz proposal for reconstructors:

https://github.com/openjdk/amber-docs/blob/master/eg-drafts/...
Ah yes, tell me more about how the exception speaks for everyone. Most folks playing Fortnite are casual gamers.
Seconding KDE + Fedora! Great twice annual upgrade cycle, SELinux by default, popular enough for e.g. a first-party Google Chrome package, and close to bleeding edge kernel! KDE feels like Windows 10 (meant in a good way).
That's available in vim via the vim-abolish[0] plugin... which has other capabilities, but the one I take advantage of is case-preserving S/one/two/ which does what you want.

It's odd vim doesn't have that builtin, I'm half convinced it does and I just haven't dug enough to find it.

[0] https://github.com/tpope/vim-abolish
> "You see, the leadership did not care about the code quality as long as the stories were delivered on time."

My problem with the concept of technical debt is that "code quality" is subjective, and more often than not it translates to "I don't like the structure of this code because I didn't write it". What matters to the business is that the code works. The owners of the business do not care if the developers enjoy working with the code or if they find it to be well written.

I hear all the time that bad code slows down development, increases bugs, etc. And that can be true in a number of cases. But most of the time it's just complaining. If a developer takes the time to re-factor the code base, it's very likely that whoever takes over from them in a few years will have the same complaints about technical debt and want to re-factor all over again.

The best way to ensure everyone's job and increase compensation is to deliver features that customers really want. Doesn't matter what the code looks like, as long as the customers are happy. Re-factoring is important to developers and to maintaining an organization. But it can wait until there aren't pressing feature demands.
Can you provide an explanation as to why it doesn't match your experience? There might very occasionally be a "killer feature", but that seems far more uncommon than features incrementally increasing the value of the product.
Interesting, because it's clear from the recording (but not the article) that the taxi instruction was read back correctly, just not followed correctly.
Dealbreaker for Mastodon (that I've seen multiple people mention) is that instance admins can view personal DMs. Yes, employees from major social media companies can view your private messages, but it's more likely there's an audit trail in those cases while Mastodon instances have minimal oversight.
Easy to say for someone who can afford to live in a single-family home in a desirable area (or, worse, get everyone else to fund roads for them). The article affects to worry about children having to ride a lift to go outside (the horror!), but those children are more likely to have somewhere to play - and someone to play with - nearby if we build densely.

The main point is a good one - we should be using better insulation and building techniques that can maintain the right temperatures in low-energy ways, and there's no point building balconies that can't actually be used. But density is needed, mechanical ventilation is not something to be feared in itself, and people like large windows and natural light.
One is business, the other one is family life. His business decisions were not right and he is learning it the hard way. Why would anyone involve their mother's death in an Elon Musk post?
Ah, thank you!

I use SysRq to REISUB my machine — but I haven't found the SysRq key on Macbook keyboards; and haven't had the nerve to enable SysRq on friend's computers (which I often end up troubleshooting), since I didn't know much about it, what the security implications are, and whether 1 is an advisable value for kernel.sysrq

Those sysctl options could make a big difference; I've wondered about something like that, but assumed the optimal default was built in. Thank you! I'll try tinkering with those values.
Exactly this. I also don’t ask permission because I consider this type of refactoring an implicit and fundamental responsibility.
I've tried to use a pi as a cloud storage but I just couldn't find a usable setup. SFTP mounts are unreliable and slow, NFS is insecure so can't be exposed over the internet, Nextcloud had the best UI but run like a dog on the pi 4.

I eventually built a full x86 desktop but found nextcloud is slow with any amount of processing power. Put 20k photos in a directory and it just stops functioning.

Gave up and went with Google Drive.
I had the same experience but never moved back from Xfce.

Is there any particular reason you've now migrated back to KDE?

What I particularly like about Xfce is that it's not very bloated. KDE always seemed quite bloated to me.
While I am aware of the extent of the morale and exhaustion problems in health care, and largely sympathetic, I must push back against the overuse of the word "collapse" for everything these days. I must have seen hundreds of headlines since the beginning of the pandemic about how this country's health care system is collapsing or that country's health care system.

Here's what an actual collapse of a health care system would look like to me:

- 95% of a country's health care personnel disappearing

- Hospitals have to close because they no longer have any health personnel. All hospitals, not just rural hospitals. And the closures must be permanent.

Since HN's crowd heavily tilts toward the US West Coast and the Bay Area in particular, I googled a list of all hospitals in San Francisco.[1]

- California Pacific Medical Center
- Davies Medical Center
- Kaiser San Francisco Medical Center
- Friends of Laguna Honda Hospital
- Langley Porter Psychiatric Institute
- Letterman Army Hospital
- Pacific Dispensary for Women and Children
- Public Health Service Hospital (San Francisco)
- Saint Francis Memorial Hospital
- St. Joseph's Hospital (San Francisco)
- St. Luke's Hospital (San Francisco, California)
- St. Mary's Medical Center (San Francisco)
- San Francisco Chinese Hospital
- San Francisco General Hospital
- San Francisco VA Medical Center
- And the UCSF system

A proper collapse of the Bay Area's health care system, to me, would entail the permanent closure of every one of the above. All of them. A "every man for himself" scenario. A scenario where there are no more nurses; no more doctors; no more surgeons. A scenario where health care requiring any kind of advanced equipment is no longer possible, where MRIs become impossible, where cancer treatments become impossible, for rich and poor people alike. A scenario where pregnant women have no choice but to give birth at home. A scenario where no one but the wealthiest billionaires can access any kind of health care that's not a Tylenol or an Advil. That's a collapse.

25% of nurses leaving within a year (and being replaced), or anecdotes of personnel calling out sick, while deeply concerning (as I wrote above, I am very sympathetic), just aren't bad enough to warrant the use of the word "collapse".

[1] https://en.wikipedia.org/wiki/Category:Hospitals_in_San_Fran...
How does this example supposed to work? When you deposit money you get an asset (an IOU from the bank), while the bank gets money + liability (they are short the IOU).

Your property after the deposit is the IOU, not the money (you gave the money away in exchange for the IOU!).

There is contract + law that governs how the IOU can be redeemed for money (up to a limit the federal government guarantees some kinds of IOUs via FDIC/etc).

Once the bank has your money (for which they gave you the IOU), they in fact can use the money at their own discretion (it is their money!) subject to some legal limitations. Those limitations are not about how banks use other people’s money (because normal banks aren’t custodial), they are limitations based on risk and collaterization of IOUs (the bank’s liabilities).

These limitations are not expression of your property rights, they are in fact limitations on bank’s property rights (their freedom to deploy capital) since historically banks were not very responsible and blew up (in which case they failed to cover their liabilities, so IOUs were redeemed for less than their face value).

Edit: as an aside, this

money => money + IOU + IOU short

Is exactly how most of “money” in circulation is produced. People take the IOU and spend it like money, banks take the money and lend it collaterized by houses/factories/etc. So you get people spending more than total cash in circulation (because they spend IOUs), while banks accumulate large IOU short position (again, collaterized through stuff like houses, factories, etc).

Nothing bad about this, this is in fact working as intended.
In fact, you should live like a hermit in wilderness and never depend on other people for anything, making your computers out of wood.
On release, IE6 was so ahead on CSS standards conformance it broke websites. The old (long-forgotten) incantation for accessing XMLHttpRequest is the way you create a COM IDispatchEx object by ProgID from inside Active Scripting, because that was the way it worked in the original IE implementation. Before there were PWAs or Electron, there was the HTA, introduced with IE5. (Admittedly XUL came even earlier.) And so on—those are not exceptions.

It’s just that once Microsoft won the web, it turned out what they wanted to do with it as the main competitor to their fat-client business was nothing, so the IE team was effectively dissolved and IE stagnated, leaving an opportunity for Firefox to displace it. But before that happened, they innovated like crazy, up to and including (by some accounts) a right to demand features they needed from the Windows team—and, on the other hand, writing the original implementations for others: multilingual UI, a Unicode layer for 9x, windowless ActiveX controls, new revisions of the common controls, etc.

So you’re right that Chrome is not the new IE of 2009: Chrome is the new IE of 1999. And unlike Microsoft back then, Google now seem perfectly happy to fund the hamster wheel if it means every other prospective browser is also forced to run inside it or lose users.
The solution is that society shouldn’t make people dependent on any single means of income for survival, not that no one gets rejected/disbarred from any occupation ever. Ultimately any negativity towards a person lies along a spectrum, and it’s important not to lose sight of the degree of harm involved.

The revoking of professional licenses is not (and should not be) intended as punishment of the individual in question, but rather limiting the damage to society of their recklessness.

That can sometimes be a slippery slope of its own, but I will argue that it’s a somewhat different slope (the “for the greater good” slope) from the “totalitarian government hates nonconformity” slope. Sometimes they intersect though.
[wyoming]
Russia could not possibly "go after" this depot. It's simply an impossible task.

There are no airports in Transnistria, and even if there were, it would be impossible to land there. Even ignoring UA and RO air defences, all of Transnistria is within UA artillery range.

Road transport is obviously impossible without Russia first capturing Odessa, which is clearly not going to happen.

Sea? Any watercraft would be destroyed by anti-ship missiles before getting anywhere close, or get shredded by UA artillery while going up the Dnister.
And yet 10 minutes before you, someone posted an archive.org link so that you could read it without obstruction. The archive.org link is invariably the #1 or #2 comment for any post that links to the economist.
I have this thing. It's just about useless imo. The CPU is so low power that it maxes out doing a file transfer making it incredibly slow. It's maybe neat if you want to tinker with open source hardware.

Also weird that they acknowledge that the GNU foundation asked them to change the name yet they seemingly won't ever do that.
Thanks karmakaze!! I have a netgear nighthawk r7000 that has the annoying habit of freezing for a couple of minutes one or twice a day, I've researched online and they say it's a firmware thing, so I thought I might replace it with FreshTomato because they say it's good and open source, I just need stable and reliable home wifi for around 15 devices
$10 million is not what is stated at your link.

"In Western countries and other liberal democracies, estimates for the value of a statistical life typically range from US$1 million—US$10 million; for example, the United States FEMA estimated the value of a statistical life at US$7.5 million in 2020." [1]

That's also not the meaning of Value of Life, which is a statistical evaluation. On a commercial plane there are almost certainly multiple people whose individual Value of Life projections exceed $10 million.

In many other cases, the value of life calculation for the very pilots of a commercial flight is less than $10 million.

This all goes to show that this calculation is not for what "each human life is worth". This is a statistical evaluation for determining what would need to be paid to an individual to engage in a dangerous activity or to be paid to a survivor after a person dies from an activity. When someone decides to work at a 7-11 in a crime-ridden area for a greater pay compared to a 7-11 in a safe family area, they perform a type of Value of Life calculation.

[1] From the first section of https://en.wikipedia.org/wiki/Value_of_life
side loaded extensions are not persisted every restart of the browser.
I think the key observation here is if the team doesn’t care about quality, you can’t create it out of thin air.

If the team does care about quality (as described in the OP), then something like a tech debt budget/carveout can be a good management/scheduling strategy to buy the team breathing room from the rest of the org.

I have used this strategy successfully in the past. For some reason it’s often easier to “spend 10% of time on tech debt” than “spend 10% of time polishing your code to avoid tech debt in the first place”. I don’t even think the latter is the correct way to build software, as you seldom know ahead of time what will justify continuous polish and refinement.

The advantage of discretionary tech debt fix time is it lets you gradually refine rough edges as they become pain points, with a low-friction bottom-up process (ie the developers that see the rough edge are empowered to fix it, rather than requiring PM/scheduling overhead for everything).
Yeah, it's also originally from the FP side. There it started I believe because people were looking how to easily make immutable updates to deep structures, since the normal way is pretty boilerplate heavy in comparison to the mutation way of just chaining accessors for an update.

And you're close, it's about using immutability to make value equality cheap by making reference equality a proxy for it. If you don't use mutations, value equality implies reference equality and is thus equivalent (since reference equality already normally implies value equality). That means you can get away with just a single pointer comparison in comparison to completely traversing both structures. This is e.g. what React does to determine whether arguments of a component have changed.

(Well, at least I also struggle to think of a scenario where both types of equality are semantically important).
There was a time I found some organizations to be paranoid about enabling it because it was mentioned in either CIS or NIST hardening but it ignores the fact that the same information can be gathered with other tools so I suppose it depends on if you have to follow a standard that still says sysrq is a risk and if your SOC1/SOC2 documentation refers to those standards as part of your audits. But in reality if that were a risk then there are a myriad of other things that would have to be disabled as well and some of those things require recompiling the kernel to disable. I am referring to the attack vector of root applications sending magic sysrq codes into /proc/sysrq-trigger

From a physical access attack vector sysrq specifically involves the Evil Maid attacks. Disk encryption, signed UEFI installations, BIOS/Firmware passwords and disabling booting from USB ports can reduce this risk a little if that is a concern. It depends on how one manages their systems and what remote management cards they have either built into the motherboard or added to the system. If disks are not encrypted then people can just power off the system and boot up on a USB drive or just steal the disks.
You raise a valid point; this lack of long term effects is also my problem with most basic income studies. That said, if you're making a decision to sell your car and move to a place near a transit stop, I'd argue that the $2.50 or whatever a train/bus ticket costs isn't going to be a primary factor in your decision.

Consider Japan; everyone uses transit there, and train tickets are generally quite expensive. But, people pay for it because:

1) Almost all development is high density near transit stops

2) The trains are fast and frequent

If we want people to use transit, low fares are a definite nice to have, but the real key is we need to stop with horrible car-centric zoning policies and low-density construction.
No, a good number of Rails devs stayed around and it became more of a mature community, but the hype driven growth/mindshare was over. There is a certain loud percentage of webdevs driven by fashion, and that portion follow the latest fashion around around. Rails lost some to Node, Node lost some to things like Go and/or React as API backed SPAs grew.

I really doubt many Rails devs went to .NET. In those days Ruby was pretty bad on Windows machines (might still be?), and nearly all Rails devs were Mac users.

I never knew .NET MVC was Rails inspired - I always assumed it would've been closer in style to the older Java MVC frameworks Rails was keen to disrupt in the beginning.
To me that means thinking about contextual information rather than "dumbing down". I don't remember anything significant being removed in the last 5 years, Dolphin is an almost perfect "power user" file manager, and they have not been messing around with it. In fact the whole Plasma desktop environment is getting into a nice stable state.

I can see it being overwhelming for someone used to an iPhone (or Gnome :p), but the KDE approach seems to be to hide advanced options/GUI by default if needed, but make enabling them a simple check box that doesn't suddenly disappear one day.
> His business decisions were not right and he is learning it the hard way.

This is absurd. His business decision worked for 16 years, which is longer than many jobs or even companies last.

The point is that the new owner of Twitter has no respect for the people who contributed to the platform over the years. Twitter won't even announce that they've shut down the 3rd party API. How cowardly is that?
Or Windows. Windows isn't even 100% consistent in style in regards to what you get out of the box, with multiple generations of old stuff always poking out somewhere.

And even MS apps have long invented their own UI -- Office has long brought its own particular controls. And the moment you install almost anything, any semblance of consistency goes out of the window.

At least GTK and KDE are two common, polished styles. For a long time it was a fashion for every random app, including technical things like antiviruses to have some sort of goofy, customized UI toolkit with irregular shaped windows. (https://i.imgur.com/P3Vu11W.jpeg)
How often do products go under because of unresolved tech debt? Is it many? When I first got into software I spent a lot of time on refactoring and cleaning up code. As time goes on I find myself doing that less and less, and just focusing on work that produces meaningful results. Fixing tech debt, from what I can tell, is less meaningful than conventional wisdom says it is.

No software will be perfect. Eventually it will die and something will replace it. I think knowing what "good enough" is, is perhaps the more important capability. Larger fruit hangs lower than tech debt the vast majority of the time.
Speaking for myself, I think that's an overly strong requirement for the use of "collapse". I'm not sure I agree that it's the right phrase for the situation(s) described in TFA, but I don't feel it would be wrong to use it for a scenario where, say, 25% of people with previously treatable conditions in fact die.
Thanks mobilio, unfortunately I have a broadcom device :(
If you like that you might want to read the daodejing, which i think that quote came from.
This strikes me as very smart -

The first rule is not to create tech debt in the first place.
The PR (Pull Request) that creates tech debt should come paired with the issue to deal with it.
Wait, your comment was something about linking (no pun intended) the Zelda franchise and pedophilia? Are you happy in your life?