skysight-inc/HackerNews huggingface dataset:
In general, criticism of this format is quite problematic and should be considered bad form. You see the format quite often in politically sensitive research and other infected areas (like nutrition), as a means of character assassination.

For any given book, you can construct a list of accusations like these, laden with quotes and references. Some of the accusations may be absolutely true (it's rare for a book to be 100% accurate), or superficially seem to be true but actually more nuanced than that in a way that is not trivial to explain, some may even be fabrications. It's hard to tell for an outsider.

Regardless of the accuracy of such a barrage of accusations, it takes an inordinate amount of time to respond to the criticism, as it will typically contain of several dozen points each of which require a lengthy response. And by that time it doesn't matter, the accusation will have already been accepted as true.

If you're going to publish something like this, you should at least notify the author well ahead of time and give them ample opportunity to explain what you've found and construct a response.
Editor, Sherlockian scholar, and lawyer Leslie Klinger took the Doyle estate to court about this idea, and got a judgement that it didn't hold. His blog about the case is at https://free-sherlock.com/ .
And if you're not a tourist, you'll be somewhere in the mile-long queue of cars stuck behind them, pottering along at 25mph gripping the steering wheel with white knuckles like they've just lapped the Nurburgring in a Veyron and panic-braking every time they see a sheep within 200m of the road.
> Even still, MacOS needs a lot of modification before it's ready for development.

Just like every single OS. Your linux box doesn't come with most of the things you listed pre-installed and preconfigured: your vim/emacs plugins, your browser of choice, git, your speicifc versions of libraries etc. etc.

Edit: BTW there's a reason there are so many tools like pyenv, or SDKman, or asdf that first appear on Linux and then get ported to other systems. Because the rosy development paradise that is Linux is everything but.

> For professional programmers, I am adamant that Linux is a more consistent experience than dealing with the issue du-jour in MacOS.

Linux has it's own share of issues du jour that impact actual use of the operating system. And most of the issues I have with OS very rarely come down to the problem with the development tools/environments/what not. Hell, I switched to M1 as an experiment about a year after it came out... and everything just worked (big thanks to those who made stuff work under M1, but even non-converted tools kept working).

And I've personally seen many people switch away from Linux to MacOS precisely because they found the overall experience of being in MacOS better. Because even if you "just" develop stuff, you still want your machine to have all the human stuff: from reliable hibernation/sleep to good touchpads to crisp displays to media support to ... yes, "touch up photos or edit video" (not necessarily for a living).
Or you realize a lot of things involving real world physical systems are hard and customers aren't fine with paying "whatever."
Also let's also keep in mind not all inflammation is bad.

As an anecdote, I know someone who had rosacea breakout and ended up eliminating tomatoes in particular from her diet and it seemed to do the trick so there should be something in tomatoes that causes inflammation...
> Both Galvani and SecondWave expect to announce first-in-human data within the next year.

In other words, this is vaporware as yet.
There's an other post at /r/southwestairlines focusing specifically on

> This 100% is at the feet of all management who refused to invest in technology updates because it is the southwest way to be stuck in 1993.

https://www.reddit.com/r/SouthwestAirlines/comments/zxg6op/t...
I can think of one intersection in my town with several accidents. It's a cross intersection with stops signs on one street and none on the other. The accidents probably all boil down to some combination of "He won't pull out" and "I'm tired of waiting." A signal light would eliminate this indecision. I fault the road design, because it requires patience people just don't tend to have to use it safely.
On Linux Mint myself. Moved away from Apple after couple years with OSX. I simply had too much friction on everything. Automation was fickle and poorly documented, package manager(s) bolted on and unstable compared to Debian/Ubuntu base, window behaviour just erratic unless tweaked and tweaked only worked for 80% of OSX apps and update system was a mess, half the stuff sort of updated correctly via app store but other half required their own install/update systems which in turn turned the clock back to Windows land in terms of updates.. not great. Also whatever software is available in OSX land is often half abandoned due to the churn on each OSX update which seems to burn software authors out more-so than is the case on Windows and Linux.

Felt relieved when I sold my Mac hardware on and could get on with computing, may well just be my usage pattern was incompatible with OSX but that was my experience.
assuming they have the data, it would be great for them to publish a report of the most dangerous roads. they could even suggest routes that are "safer"
The industry is really good at inventing the wheel multiple times. Even in a simple case: Two car manufacturers, same supplier for the same kind of control unit - the hardware will likely look similar, but most likely both are running almost completely different software.
Maybe? A one second glance could put you in the mindset where you're ready to brake hard, or put some extra distance between you and the car in front, or choose to not search for the next song you want to hear, etc.
U.S.-listed Chinese tech companies cancel HK-listing plans
It puts the term 'softsynth' to good use. Incredible, really.
They obviously weren’t counting on a massive multi day storm when originally selling the tickets.

Their inability to get themselves out of it was clearly a failure that article discusses.
Haha, of course!
Same here. Different hardware (much older) and Windows 11.

Haven't rebooted that machine in weeks either.
massively complex and insanely unstable, everything hinging off the long since gone consultant created, Rube Goldberg chain of RPA bots
Muscle memory to know that the third button in past the volume knob turns on the windshield defroster, vs. looking at a menu on a screen whilst driving...
If you're just working from home this setup would be great:

4k 28" monitor -- ~250-300 + tax
Aeron chair -- say ~300 used or the Costco office chair which IMO is comparale comfort
Sit stand desk from Costco -- $300
M1 Mac Mini 16/512
Clearly given it was reopened after providing more details this was a misunderstanding or triage mistake. Given the volume of reports this must happen all the time, and was resolved here as expected.
Reminds me of this Onion headline: "Smart, Qualified People Behind The Scenes Keeping America Safe: ‘We Don't Exist’"

https://www.theonion.com/smart-qualified-people-behind-the-s...
It's worth drawing a thick distinction between rheumatoid (autoimmune) and osteoarthritis (worn out).
> would have learned Impress up to a level.

Oh, Impress is basically the same as PowerPoint, the differences are not significant. Here's a 11-minute video exemplifying the experience of creating a simple presentation from scratch:

https://www.youtube.com/watch?v=DDmEvjs4iBw

... frankly, I wouldn't even watch it, just pretend PowerPoint came out with a new version where they tweaked the UI a bit.
LastPass disclosure of leaked vaults is being torn apart by security experts
I believe this has changed in recent years due to similar hiccups, and their reliability in prior years was previously good.
Adobe Lightroom has it. Unfortunately it is quite expensive for the casual photographer.
Not if you plug them in.
I would write that as either "faw lah lah" or "fuh lah lah" or maybe "fuh luh luh". The "paw" sound is undeniably how I'd refer to my father, not "puh", or "pah", though I could imagine like a New England accent using the latter.
> There's no way to verify you're getting the original prompt.

(author here) I do suggest a verification method for readers to pursue https://lspace.swyx.io/i/93381455/prompt-leaks-are-harmless . If the sources are correct, you should be able to come to exactly equal output given the same inputs for obviously low-temperature features. (some features, like "Poem", are probably high-temp on purpose)

In fact I almost did it myself before deciding I should probably just publish first and see if people even found this interesting before sinking more time into it.

The other hint of course is that the wording of the prompts i found much more closely match how I already knew (without revealing) the GPT community words their prompts in these products, including templating and goalsetting (also discussed in the article) - not present in this naive Jasper attempt.
Ugh I hope not. But that is incentive to migrate away from google serivces.
> USB3: The micro-B "3.0 appendage" is ridiculous and huge, and no device which uses micro-B ended up supporting it in practice (except for I believe a couple Samsung phones?)

Nearly every external portable HDD I've seen has these (and comes with a corresponding short USB 3.0 micro-B to A cable).
I recommend it. For me, unused skills will become inaccessible relatively quickly, and interviews require a specific set that aren't used at all in any of my jobs over the years.

Once, I did heavy interview prep because I was bored with my job at the time, I got good at it, and landed another better job.

A year later my company deleted entire orgs of people, and I quickly realized that I was in bad shape when my third rejection rolled in.

Interviews are high pressure situations. Better to be used to the flow, coding, and conversation style (again, think "sales") than to be caught off guard, worrying about whether you've solved a Leetcode question fast enough to satisfy another human with their own grading quirks.

Oh, and that person is standing between you and a steady paycheck. That's the part I have to practice anyway, solving stupid university final problems when my livelihood is on the line.
Hebrew script but not in Hebrew.

The first recipe in Hebrew would probably be Ezekiel 24(א) but it's all a metaphor for a badly behaved city (Jerusalem). Lots of dietary laws in there too, naturally, but also sitophilia:

סמכוני באשישות רפדוני בתפוחים כי חולת אהבה אני (ב)

(א) 3 Thus saith the Lord God; Set on a pot, set it on, and also pour water into it: 4 Gather the pieces thereof into it, even every good piece, the thigh, and the shoulder; fill it with the choice bones. 5 Take the choice of the flock, and burn also the bones under it, and make it boil well, and let them seethe the bones of it therein.

(ב) Stay me with flagons, comfort me with apples: for I am sick of love.
The problem isn't the machine-readable encoding that indeed happens to use the ISO YMD ordering, its that you can have a site that's in language/culture X, which includes dates related to whatever events or moments are relevant, but also includes a form with a date-field ordering that is _different_ from that of the text and possibly date fields, and _different_ from the convention in language/culture X.

Actual human language is context sensitive. The user's date formatting preference is almost a non-sequitur even as a concept. People fundamentally can't pick whatever date formatting they want in general-purpose content; they'll need to be able to understand whatever is the norm in that context. And in most contexts while there are various date forms, they're usually not (problematically) ambiguous. As long as a user stays within one date-formatting bubble, that's fine, but it just works really poorly if a user does not. Within an application that's primarily concerned with dates and in which every date is a specially typed value, like say a calendar - sure, date formatting preferences are feasible. That however describes a rather small fraction of the overall web. And the textual, machine-comprehensible hypertext web itself, while eating the world, is itself still only part of culture; dates are visible in videos, images, books, magazines, etc - and they make sense in those contexts _in context_ - i.e. _not_ using the client's date formatting preferences.

If a user's date-formatting preferences were to really have meaning on the web, you'd need to ensure that even dates in plain text or written summaries satisfy that formatting, and hope that videos and images rarely are mixed with such text. But that's just not the norm, and likely completely impractical; it'll never happen, especially not given the reality that many dates are manually written by humans without any markup at all. And where software tries to "fix" that - well, you get disasters like Excel, which is notorious for causing insidious data-corruption by trying to guess data-types in pretty creative and unhelpful ways.

In practice that's not what sites _actually_ do. They either have really simplistic date handling, in which case date controls can be confusing but rare enough that it's not hugely impactful, _or_ they use custom date controls (the actual norm). And that makes browser date controls _even_ worse, because those will then unpredictably not use the context culture, but instead the client's culture - unlike most sites, which don't use input type=date as far as I can tell.

The correct solution would be to allow a site to specify the site's culture and formatting settings, much like language can be specified. And if none is specified: sure, fall back to the user's date preference.
Yeah I need to tweak a bit between xrandr scaling and xdg dpi, then force specific apps as well. Not ideal, but enough tweaking got it done.
I love in the real world and know that’s nonsense. So, if I poll 10,000 defense attorneys, 90% or more are going to tell me this childish nonsense. What if I polled victims of crime, let’s include victims of police crime, my guess you might think the majority of crime must be done police.

Actually, by your logic, you must think the vast majority of crimes or an enormously significant amount of crimes are committed by police because you claim trusting police will get you killed or jailed. However, it is certainly true that enormous numbers of people “trust”, in some sense, the police but the problem we do not see the numbers of those people being killed/jailed to support your position.
in case you really didn't know, "they" can also be singular

https://www.dictionary.com/browse/they
Tradeoffs, we agree. I fight CF because I am so often on the sharp end
of their stick.

I see that many of your personal concerns stem from the wish to be a
good netizen yourself.

FWIW, I deeply value these discussions. You've made some new points,
noted and helpful for my research, thank you.
Restartable Sequences “RSEQ” Additions Expected for Linux 6.3
Hm... you might be able to get away with ordering a EU UPS then, those are 240V, you'll have to add a center tap transformer and maybe mess around a bit with it to get it to output 60 Hz (that will only improve efficiency).
Does every prosecutor not care about the truth? No, of course not. Plenty of prosecutors and police officers actually care that they got the right person. But, there's a lot who only care about chalking up a win and closing a case, not actually getting the right person. There are stories in the news all the time about folks being released after it was discovered they were innocent beyond all doubt after a conviction

> It fails basic logic because from this premise, the police abs prosecutors are ready, willing, and able to prosecute and largely convict innocent people and it is in their benefit to have high clearances. What explains the disparity?

It also looks bad if prosecutors are railroading very obviously innocent people. The only reason it's happening as much as it does is the poor saps who get caught up don't have a very clear alibi or other evidence showing their innocence
Why would you think that the EU can't regulate whatever wireless standards Apple chooses to use in the future as they are doing with current wireless technology?
> I miss the raw efficiency, unparalleled speed and superior ergonomics of my i3wm bushido

I'm in the same vein as you. I tried to be productive on my m1, but as a 10+ year rusted on i3 user, I cannot for the life of me ween myself off it.
https://releasehub.com/ (Disclaimer, first listed because I work here)

https://www.quali.com/

https://www.withcoherence.com/

https://webapp.io/

https://www.uffizzi.com/

https://www.qovery.com/

https://www.devzero.io/

These exist in the B2B space (and isn't an exhaustive list), there are a ton more in the B2C space
What I don't get is, why would I want there to be a third state in this boolean example? You're saying it could be useful. That's true, it could. However, we're talking about something that today is already just a boolean, such as "is_published." Even if you can envision a reason why you might want a third unknown state for "is_published", if you write a bunch of code that treats it as a boolean, without knowing what the null state might mean, you are not solving a problem. You're just modelling your data slightly less precisely. Saving a date is saving known, useful state, even if you don't need it yet. Using a nullable type for a field that can't yet be null is just adding an additional unknown state for no reason.

When using Go and sqlc, what would happen is I would use a NOT NULL field for the boolean, because I'm modelling a boolean, not a tri-state. If I was modelling something where I had three states I wanted to handle, I would use an enum instead. But even if I wanted to use NULL instead of an enum that explicitly specifies the meaning of the third state, I'd rather start as NOT NULL. Why? Because then, if I ever want to remove the constraint, I can. And when I do, sqlc will helpfully change the type of the field from a raw boolean to a nullable boolean wrapper. And doing this will break the existing code. This is good. Why? Because in every place where I assumed there were only two possible states, I can now check and see what I'd want to do in my new third case. This is better than starting with nullability, because if I don't know what NULL means or why I'd have it, it's really difficult to know what my code should do when it encounters it. You could always throw errors, but if you do that you have to ensure you clean all of that up before you start actually using NULL.

This is fundamentally about data modelling though. Talking in this abstract sense is not useful. What I feel you're failing to make an adequate case for is why a field like the one described in the linked article needs a state other than "set" or "unset". Just putting a nullable timestamp is a nearly free upgrade from putting a non nullable boolean, which is what I would've done anyways.

If I want to add more states, I want explicit data model changes, that result in explicit test and type checking errors, that highlight wherever I need to update my code's state management to account for new states.

Additional note: particular to SQL, removing not NULL constraints is basically free from the database end as far as I can tell. In addition, NULL has specific behaviors, especially w.r.t. JOINs, so I would NOT want to use NULL to model a tri-state.
Yes, but Xerox unfortunately never managed to turn their great ideas into a (commercially successful) product. Otherwise we would perhaps all work with Smalltalk or Lisp machines today - or maybe Oberon, Niklaus Wirth's work was also significantly influenced by his sabbatical at Xerox PARC...
Yes, and if you're in the game thru a few downturns, you will be laid off during them a few times in an otherwise successful career. Severance package FTW.
Amazon’s started to deliver orders by drones in California and Texas
How and why did the Bay Area become so liberal? (2020)
How does it work with borrowing physical books from the library and me not paying a late fee?
Part of it is, indeed, talking about unspoken rules. But part of it is that the hiring managers and CEOs are humans like everyone else - some may have ego issues, or buy a little too much into their company's branding.
> I don't get how people who like modal editing can't accept that other people don't.

Hi. I like modal editing and kind of can't accept that other people don't.

I think they just haven't really tried, you know? In my view, it isn't a subjective matter of preference, rather I consider modal editing to be objectively superior: we have the whole keyboard at our disposal to enter commands and manipulate the text, not just tricky key combinations.

Sometimes the objection to modal editing is that you need to keep an eye on which mode you're in, but in my experience. If you're doing it right, you're always in normal mode, unless inserting text. When you finish inserting text, you immediately switch to normal mode.

There, I probably haven't convinced you nor anyone else, but I'm sure all the vim users are nodding along ;)
worth mentioning that Vulkan is the only API that runs on all three major platforms. Natively on Windows and Linux, via MoltenVK on MacOS.
Doesn’t it feel that, since COVID, we keep hearing more and more about these colossal, systemic failures more frequently? It makes me concerned because it seems most assume that at least someone knows what’s going on. Whereas the reality is that almost no one, if anyone, actually knows what’s going on, and that we have fragile software systems “running” everything. And COVID seems to have been a real shot to the brow for many of these systems.

I just worry about what hell we’re creating. Software basically captures miscommunication and poor understanding and executes it.
samdauwe's work is fantastic. We're using WebGPU in Mach engine, and also have quite a large set of examples for how to use WebGPU from Zig[0] that are pretty much standalone (only use our engine for windowing/input), may be a bit easier for folks to run (zero-fuss installation, you can cross compile seamlessly to any OS, etc.):

[0] https://machengine.org/gpu/
What is wrong with people 'simultaneously' being able to read an eBook?

I feel like I'm missing something obvious.
"No, it’s not going to make the world a better place. Yes, it might even make the world a worse place.

But you will be employed."

With the same attitude DuPont managers dumped PFAS into the rivers.
> There's a reason Netflix is still on AWS.

I would counter with stack overflow which has scaled great over all this time on only a few self-hosted servers.

The trouble with replacing the buy with a diy later on is that it will now cost at least twice as much to build, because 1) you're maintaining the existing system which takes some of the people most familiar with the problems of the existing system, and 2) the existing system will still evolve a bit because that's business, so you're also trying to hit a moving target.

I think other posters have it correct, you have to think hard about how central a particular feature or service is to your business model. Chances are, differentiating yourself means off the shelf solutions won't be a perfect fit for your core revenue, but all other supporting services should probably be off the shelf.
Private Equity.
The Peach Press Dreamweaver 4 book is listed on Sell your books at £0.46. I’m surprised it’s worth that much, the postage and packing would be far more.
Don't know which features of the Linux kernel OP expects to be of importance to developers, but (historic perhaps) to us it (painfully) mattered that Linux kernels before 3.10 didn't support docker fully. Every now and then, there is a feature that matters to userland.
Wouldn't the same effect be in play with family-living animals that aren't nearly as long lived? Like wolves for example. In fact all the other great apes only hit about 40 years before succumbing to old age, whereas humans are nearly double that.