skysight-inc/HackerNews huggingface dataset:
That's pretty impressive performance! Was just looking over at their github repo and documentation and I'm tempted... because I definitely need yet another project :)
It's small, but spacious. The Fully Charged reviewer is 6'6" but fits comfortably in the back seat behind a front seat set for him.
The real question is: why didn't they get booted out earlier?
I don't believe any state does not accept a US passport as ID, and would need to see a source on that. A quick google returns no results.
Uber and Lyft agree to pay drivers $32.50 per hour in Massachusetts settlement
ratatui.rs is a library, whoever reads that changelog are potentially interested in the nitty gritty details. But I'd say it is the exception rather than rule, and even in that case it is only sensible for projects of a certain size with a certain release cadence.

Still, stuff like:

7a48c5b (cell) Add EMPTY and
(const) new method by @EdJoPaTo in #1143
This simplifies calls to
`Buffer::filled` in tests.

feels questionable to have in the changelog either way. Unless that for some reason has a great impact for users (could be, didn't read into it).

A better example, in my eyes, is teamcity.

https://www.jetbrains.com/help/teamcity/what-s-new-in-teamci...

A curated overview that actually explains the change rather than just states a difference.

They also have a similar view of fixed tickets: https://www.jetbrains.com/help/teamcity/teamcity-2024-03-rel...

Doing what teamcity does takes some effort. And I guess my gripe is the belief that these conventional commits will save the majority of work of the release notes. It can be a convenience but it needs curation and work to be presentable. And most projects seem to pick them to avoid that work.
Are there software systems being developed (and which can be developed) where the engineers, server admins, dev ops etc have no access to the production data? Is that possible to achieve? Do all data have to be encrypted for that to work? And how are the encryption/decryption keys handled and still allow the devs/admins to do what they need to do?

Right now it feels like most systems have an okay security level and authorization model for the end users and admin people in the office, but then behind the scenes, on the server, almost any random dev or consultant can access the raw production DB and do what ever they want.
I think it's a good idea, but a very different type of problem. It'd be really cool to build, but I think you'd have to start from scratch.

It'd be very hard to extend the existing solution to meet that use case.
It's interesting you say that, coming from Toronto, I was floored at how _well_ NYC traffic moves in comparison. Obviously no city is perfect, but suggesting that NYC is "incompetently managed" is a little funny to me. Of the other cities I've lived in, Seattle, Vancouver, SF, and Toronto, I've found the NYC city services to be by far the most effective.

What US city do you think does a better job?
https://www.latimes.com/socal/daily-pilot/news/story/2024-01...
Nice work! That's a lot of great resources.

Only feedback I would have, is that if you wanted to be more identifiable/discoverable most projects like this are called "Awesome <something>" such as "Awesome Elixir". If you called it "Awesome Elixir" people would know at a glance what it is. It would also probably make your project easier to search for.

Thanks for sharing!
I hate flying with passion and get extremely scared when flying through turbulences but, there was a journalist in my country, that also had experience as a pilot and said once on TV that during turbulences, is one of the safest moments in a plane. I don't remember the reasons but is there anybody in here with knowledge in the field that could confirm/deny this?
I find that some keyboard shortcuts, in programs that use "weird" keys like, say, Alt-semicolon or Ctrl-backslash, don't work with a Nordic keyboard. I've hypothesised it's because we need to use modifiers to get to those characters in the first place; maybe the programs read keyboard scan codes directly in stead of OS-mediated character codes (or vice versa), Idunno... You never run into that?
I have a friend who is allergic to sesame, this law was really frustrating for her. The brands who purposely added sesame to comply with the law she couldn't eat anymore, the brands that just added the label she also couldn't eat because she couldn't tell the difference between the two. Before the law if sesame wasn't listed it meant it was at worst trace amounts and if it was listed it was off limits.

She isn't "immediately dies on contact" allergic so to solve this problem we had a "loaf party" where we got one of every brand of bread in the grocery store, she would get to try all of them and each person goes home with the rest of a loaf. It was fun all things considered but silly that it was necessary.

So yeah, I have no idea why the fda did this, it seems worse for everyone involved.
How convenient that they're this quick to find evidence of a Russian APT when attribution is usually one of the more difficult things to do well in IT security.
It has nothing to do with profit, as it'll just increase the price of the goods to the consumer.
Has anyone found screenshots?
I feel like there are some really important details about this missing.

First off, are there really a loss of sales of heart monitors because of this? I would think that the only people who had real time heart monitors are those that were given it by a doctor and that would not change with the apple watch given the FDA clearance.

I know for myself, I have no need for a monitor all the time so the apple watch doing anything is a bonus since its nothing or the apple watch at this current time with my health.

It would also be helpful to know why apple made this change in the first place. That is entirely glossed over by the article. Even trying to google this topic the best I can find is that apple believes the new algorithm is better.
Do you think the idea of binary analysis does not exist? Or that courts don't have a long history of deciding questions of judgement? The problem is also fundamentally quite similar to proving that a published binary is/isn't a derivative work of someone else's work.

Also handcrafted assembly isn't sufficient for your argument, but rather one would have to directly write a binary with a hex editor. Show me any binary larger than say 1 MB that was written with a hex editor. So really the burden of proof would be on anyone claiming that a large binary is direct creation.
I like Svelte too, but take another look at Angular. Your memories of Angular 9 don't match up anymore. It's A LOT more streamlined now with so much less boilerplate than before. And signals.

That said, transitioning to some backend or infrastructure focus never hurt anyone. It's good to see problems from different perspectives and roles. No one ever got fired for knowing too much SQL.
Every single keyboard layout has its own story. Let me tell you the one about the keyboard layout I use: CAN/CSA Z243.200-92.

When writing French on typewriters, people in Québec and the rest of Canada used a slightly modified US-keyboard layout that assigned the necessary accents and moved the symbols those keys used elsewhere. You could even use this layout with the US 104-keys keyboards on computers without losing much. Aside from having glyphs on your keys that didn't connect to what you were typing but people lived with it.

But when we moved to computers there came an opportunity to improve the keyboard. We could now assign keys to common letters with their accents together without losing anything, since we didn't need to focus on the additive nature of accents. You know, moving from a mechanical system to pure software.

So who jumped on the opportunity? The government of Québec led the charge in the early 90s for this new keyboard layout to replace the old French (Canada) layout. Feeling at some point that there was a risk of furthering divide in Canada, the federal government asked for some slight changes to the Québec proposal, in exchange for the promise of adopting it as the standard Canada-wide. Québec agreed, but Canada never did anything of value to help with adoption. So we're stuck with two standards, basically on the line of your OS: if you're on Windows, you're probably using the old French (Canada), and Mac users switched over to the new standard.

Every. single. keyboard layout. has a story surrounding its creation and its usage.
Really great resource. If you want more of a book format, I also highly recommend The Linux Command Line by William Shotts: https://linuxcommand.org/tlcl.php
Probably is by the time they are found, the rhino is dead. They might catch the last guy holding the bag, but I suspect it's passed through a few different groups by the time it reaches the airport. So the poachers just go on poaching as they already got paid.
Ah genuniely missed that line, though as the FDA states is legal.
The biggest bidder ? /s
Given Apple's sizeable chunk of the market, it makes sense to give 3rd party developers programmatic access to certain platform features. This way, changes to Apple's own apps wouldn't be so impactful, and they can continue to innovate in parallel.
Racist stupidity at its best in the comments.
The fact that I can go months without updating a rolling distro and things very rarely break is incredible. Tumbleweed is rock solid. (Personally, I've never experienced a break, but I know one just happened for a lot of people. Granted, I believe it was Nvidia or Mesa drivers at fault.)
If we are going all in on imaginary civilizations, even a very narrow (well, not that narrow) frequency band could be used to encode information, couldn't they?
New account too. Good catch.
My suspicion is that Apple switched monitoring types to better manage battery life and to continue to walk the fine line of the Apple Watch not actually being a health device (from an FDA perspective)
I won't comment on the specific numbers or enforcement mechanisms. But I strongly agree that we need reasonable SLAs for the government. My only worry would be how to deal with abuse.
Do you recall why they said it was the safest? My first guess is because the pilots are paying more attention while flying through turbulence.
The typical Markdown answer to needing indentation preserved is the "code fence" (triple backquotes ```), though I imagine the problem with that is that Obsidian by default stops dealing with Wikilinks inside fenced code. I don't know Obsidian that well, but maybe there's a way to use a code fence and have it support Wikilinks inside?

A different direction to explore might be to explore proportional font coding techniques that rely less on whitespace. Lisp can be a good language to play with those ideas given whitespace isn't syntactic. Though idiomatic Lisp has certainly relied on semantic whitespace in coding styles for a very long time.
Try not to write code like this in statically, nominally typed languages (Java, Kotlin, C++, etc.). Without a good compile-time metaprogramming, you're bound to need code like this sooner rather than later [EDIT: you still should try to minimize it; it shouldn't be the first solution you reach for, but it really is unavoidable in many cases]. It's a PITA, but that's just it is in those languages - and Copilot works pretty well as an ad hoc code-gen tool.
Probably fake login portals
I think the issue is that by changing the way watchOS works, Apple effectively removes the possibility to develop a 3rd party health-tracking tool (because the sensor data is no longer available).

Imagine AliveCor (or anyone) coming up with a better way than Apple to interpret data from the device. Or they use the data in a different use case than the watchOS health feature... there are many reasons to enable 3rd parties access to onboard sensors.
Would be interesting to see one for the Linux Kernel. Each include an edge on the graph
"For all the remarkable recent progress in AI research, we are still very far from creating machines that think and learn as well as people do. As Meta AI’s Chief AI Scientist Yann LeCun notes, a teenager who has never sat behind a steering wheel can learn to drive in about 20 hours, while the best autonomous driving systems today need millions or billions of pieces of labeled training data and millions of reinforcement learning trials in virtual environments. And even then, they fall short of human’s ability to drive a car reliably."

PS. Some teenagers ... :)
I think too much stability is self defeating. It creates fragility like a monocultured ecosystem. Self correction mechanisms are important, even if they're painful. Bad governments and bad enterprises need to be wiped out now and again by war and recession, as a last resort when other forms of reform fail.

Britain never seems stable at first glance. Read a newspaper from 5, 50, 150 or 250 years ago and they'll all be lamenting economic uncertainty, geopolitical dilemmas and social injustice. Yet in that time no revolutions have killed more than 1% of the population, long term economic growth has averaged couple percentage points annually and nobody has successfully invaded the Islands.
> People use it - like I do - because they like the improved type safety compared to REST.

You don't need a binary format just to get type safety. JSONSchema, OpenAPI, etc exist after all.

> But in this case the DSL is OpenAPI, which is an error prone mess of YAML or JSON specifications.

They might not be pretty, but they're not particularly error prone (the specs themselves are statically checked).
> separation of powers issues ... in the background

Under the Exceptions and Regulations Clause in Article III, every federal court exercises its power at the sufferance of Congress (apart from cases under SCOTUS's original jurisdiction). Securities-fraud cases brought by the SEC are creatures of federal statute, not (non-existent) federal common law (cf. Erie), and so the Seventh Amendment jury right arguably doesn't apply. Under the E&R Clause, Congress could authoritatively say so, overruling past SCOTUS ipse dixit extensions of the Seventh Amendment to analogous cases.
It's a murky issue, but I think it really comes down to how much we trust the Chinese government. I don't, not at all, and so long as the Chinese government controls TikTok I will support the forced sale.
There are many foot-guns to be found in bash scripting.

I highly recommend the Wooledge wiki for any and all bash knowledge, it points every place you can go wrong, especially when using advanced features.

https://mywiki.wooledge.org/FullBashGuide

http://mywiki.wooledge.org/BashFAQ
Supreme Court overturns 40-year-old "Chevron deference" doctrine
You may be right and I may be guilty of hindsight bias, but I would probably put this in the realm of BS. It’s not like opioids were unknown to cause addiction, and when physicians witness the company continuing to up the dosage and wordsmith terms like “breakthrough pain” I would expect a cognizant doctor to be throwing red flags.

To overextend the mechanic metaphor, it would be like making a part out of aluminum and claiming it has infinite fatigue life. We know aluminum doesn’t so the threshold of evidence needs to be very, very high or the mechanic should remain skeptical. If the part continues to fail, but the manufacturer keeps making new, novel excuses the mechanic should be throwing the BS flag about their infinite fatigue life claims.
My guess is Google wanted to really give them every opportunity so that most people come to your conclusion instead of "wow! Google is just trying to censor the internet"
Ask HN: How to reuse waste heat and water from AI datacenters?
Quote of the century
last update 2014

that being said, it think 10 years later, linux should pick a data oriented shell (powershell or nushell) and go full in on it

on windows, almost all services have some Powershell support

i understand that on linux, command line support is always there, so unlike windows adding command line support is not really news, but still i think the move to a data oriented shell, is better
Also, they just looked at 2 years, so there could be cherry picking. Jet stream is affected by el nino. 1979 was weak el nino, 2020 was moderate la nina.

https://ggweather.com/enso/oni.htm
> Yes, this is pretty much a conspiracy theory.

Which part?

Unit 8200 as an incubator for tech startups is well-reported: https://www.calcalistech.com/tags/Unit_8200

The security complex intertwined with "hitech" and economy is well-tracked: https://www.calcalist.co.il/market/article/jh6p1lmcb

The intention of its most popular leaders to expand existing territories is well-studied: https://www.jstor.org/stable/2537218
Daily multivitamin supplements don't help you live longer, study shows
Can someone ELI5 what the violations linked in the first line are? They seem pretty minor to me but I don't understand certs
You are right, what I claimed is byond the current scope of science. It is a bit like saying 'A brain can "see" an apple even when the eyes are closed" (alluding to what we call "imagination"). You _know_ it can, but science can not prove it. It is based on your very own experience
Dup: https://news.ycombinator.com/item?id=40807392
PS. Wait until they start hitting the AI field ...
If you dig in a bit, it's a fairly minor scandal. There are much, much better summaries elsewhere.

I've gotta point out though, the writing in that article is truly abhorrent. This is the weird Frankenstein of The Onion and Gawker that was picked up by private equity, right? The web is a better place without this style of publication, I think.

I'd encourage you to get your news somewhere else my friend :) This reporting makes Buzzfeed look Pulitzer worthy.
Mine are all the same colour, so no help there... But generally, ÄÖ is Swedish / Finnish, and ØÆ / ÆØ is Danish and Norwegian.

But which of the latter two is which, and why on earth did they flip those two around between the languages??? So fricking weird...
Project Schedule Free Template
Nixos is pretty slick for servers. Everything from users to nginx to system services to firewall is defined declaratively in 1-5 files, and deployment is as simple as `nixos-rebuild switch -—target-host deploy@host`.

For me that’s pretty wild. It makes it trivial to have both staging and prod in sync by just pushing to a repo. That means you get a better overview of the system state, and can experiment more freely knowing the machine won’t end up in a weird state. And while Nixos is hard to debug and occasionally hard to write, I find the format very easy to read.

However for my personal computer, I found that it’s overkill and now I just use a dotfile manager and save my installed program names in a list. I do think nix really lacks documentation for very basic things, and for that guix is better (but I found guix harder to write and read).
They had to blame something like a state. Else they look incompetent. /s
The solution to this is obvious. We need to ask each denomination supply gladiators\W\W\W\W\Wmissionaries who will debate the finer points of doctrine with warhammers. Once everyone agrees there's a winner then the winner gets to decide what is taught in schools. To register disagreement, more gladiators\W\W\W\W\Wmartyrs have to step up. It'll provide a safe outlet for that overpowering martyrdom complex, it'll be entertaining, and it'll never get resolved.

Vote for me in 2024.
Even notaries don't need to keep copies of licenses or selfies on hand for court, just their notarial register.
Somewhat discussed here in this earlier submission: https://news.ycombinator.com/item?id=40812833
IME most companies that take this seriously do have some kind of access to prod for debugging/etc but it is strictly monitored, time limited and requires approval. Often it also has contractual controls too.

GCP offers a special paid product to provide customers more control over google employee access to your systems. It's called assured workloads https://cloud.google.com/security/products/assured-workloads...

Specifically the container.restrictNoncompliantDiagnosticDataAccess org policy is... Interesting.
Once you've been out of a city for a while the smell of car exhaust can be extremely strong.

Every time I fly into LAX from northern Canada I get a punch in the lungs - it's horrible. There must be some severe long-term health impacts.
Thanks for giving it a try. Super glad it worked for you
As you may recall I said I strongly dislike React. You are preaching to the converted with your complaints. That does not alter the fact that junior developer needs to know React since for better or worse (worse) it is the de-facto standard for front-end development at the moment.
Except because of prop 65, I learned that some bowls actually do have some lead in them due to their glazes or coloring…

And that the label was probably correct.
I think they meant to say specifically Leap 15.3
> I don't know if this is the case, but if the life expectancy of rhinos is much less than humans,

Luckily this is easily obtainable information on the internet.

'Rhinoceroses’ lifespans vary on species. A rhino’s lifespan is typically 40 to 45 years."

https://www.pbs.org/wnet/nature/blog/rhinoceros-fact-sheet/

That is less than a human lifespan but not by orders of magnitude smaller. Sounds like a very narrow needle to thread.
It is safe because you are flying. Airplanes almost never have issues at altitude. Problems occur when closer to the ground. Landing/takeoff are the most dangerous times, the transitions between flying and not flying.
> The poles warm FASTER than the equator

The article cites the Prosser Report which contradicts this claim, but I find it hard to understand how this could be true for very long. Why wouldn't the atmosphere stabilize as gradients diminish?
> string, list, map, etc? You have to use an encoding scheme.

Yes, you have to use an encoding scheme like JSON or Protobufs. Dumping memory directly down the pipe as you're suggesting doesn't work.

> As for go / javascript? I think most languages have the ability to inspect a raw buffer.

No language has the ability to read a raw buffer and know what the contents are supposed to mean. There needs to be a protocol for decoding the data, for example JSON or Protobufs.
Avoiding request boilerplate, in and of itself, is a benefit I could take or leave. Boilerplate request/response code is boring, but not actually time-consuming to write.

What I really like about the IDL and codegen is that it makes inter-team coordination easier. Comments in the .proto file is much nicer for documentation than, e.g., Swagger docs. And it gets even better when you're negotiating protocol changes among teams. You can just start a pull request with the proposed changes to the message format and documentation, which makes the whole process so much easier (and more accurate!) than what I've experienced with negotiating protocol and API changes for REST-style services.

And then, after it gets merged, the rollout is more likely to be successful. With REST, the risk of regression is greater. You've got to contend with ill- and implicitly-defined backward compatibility semantics that are inconsistent among different JSON and request library implementations, and you've got to contend with greater risk of each team's implementation implementing the message serde code in subtly incompatible ways. protobufs and gRPC don't eliminate that risk, but they greatly reduce it.

That said, yes, you're right, it does often feel like gRPC often steps over the line from being sensibly opinionated, to being a way for Google engineers I've never even met to micro-manage me. I wouldn't say I'm a hardened skeptic yet, but I'm definitely no longer a fanatic.
Ooof missed that, thanks!
Carl Shulman on the economy and national security after AGI