skysight-inc/HackerNews huggingface dataset:
For US/UK/NZ/Aus/SA, ISBNs are granted through Bowker who does maintain their "Books In Print" data set that, in theory, contains metadata for all of the ISBNs they've granted. In practice though it's a mess. It's expensive to access and relies on publishers to enter in accurate and consistent metadata, which is...variable in quality to say the least. Often publishers buy blocks of ISBNs to use later so no metadata is entered up front and has to be pushed back to Bowker at a later date. To be somewhat fair to Bowker, the history of ISBNs far predates modern data standards and I can imagine wrangling publishers to get accurate data is a difficult task. But on the other hand, you'd think they'd have a lot to gain for doing it right. As someone who runs a book website, it is endlessly frustrating.
Well, on Android I had Do Not Disturb on as a test today and the alert was silent but still received - saw it when waking my phone.
(The next leading market share is Walmart's 6.3%.)
I hate that podcast so much. It's practically unlistenable. There's so little content and just lame jokes. I'm always surprised when people recommend it.
This prompt was a key step forward in the field of human pedagogy as well.
Exactly my thoughts!

The article and many commenters here all talk about programmer ergonomics, productivity and "correctness".

The current research shows that these things are neither improved nor weakened by static typing. There are (even recent) papers on comparing typed vs dynamic language with no meaningful results. So basically it's entirely subjective.

However there _is_ an actual effect of static typing that can be trivially proven: It enables a programmer to write more efficient code. That should be at the forefront of every discussion around typing discipline, because everything else is just _hot air_ at this point.

TypeScript (used in the article) is an example that is _not_ actually strongly typed (it's statically typed but weak) and it doesn't even provide performance and memory layout guarantees, because the types are just comments. So you pay all of the cost of static typing without _any_ of the tangible benefits except documentation.

To me it is surprising that we as a technical community completely ignore actual evidence and take our cultural and personal preferences as fact.
What is the point of that? You drop phone in toilet and it stops working because the battery circuits are damaged, or the charging port is damaged. It might be cheaper to fix that way.

Phones currently can be dropped in the toilet with zero damage. It is a real benefit to have waterproofing. I would prefer waterproofing over easily replacing battery that happens rarely.
In Intellij you can add breakpoints to when lambdas are executed [0]. You can also print logs instead of suspending the threads [1].

[0] https://www.jetbrains.com/help/idea/using-breakpoints.html#s...

[1] https://www.jetbrains.com/help/idea/using-breakpoints.html#l...
Wrote any assembly recently?
That was pre-COVID. During and post COVID, the exodus is back on again. China is in a stealth recession right now with high youth unemployment, so there are still economic factors driving this.
I think most people would agree that types prevent a lot of bugs (and others posted research to support it in the thread), so the question is less about that and more about the subjective reasoning people have to decide the investment is not worth it.
Okay, perhaps you're going to go the literal route with this. No, this is not instantaneous censorship. I'll say it this way: they are creating the tools with which they will inevitably enforce censorship on those with enough reach that they dislike.
To the New Yorker's demographic, race is central to everything. They feed an audience who fetishizes finding racism in the most obscure nooks and crannies of society. The piece is written to be pure self-masturbatory confirmation of "good" values for people who live in wealthy enclaves of coastal urban centers.
How about AI generated profiles? Befriend an AI, live life like The Truman Show.
This will not help a jot with online play, but it’s worth noting that it’s very very easy to softmod any model of 3DS: https://3ds.hacks.guide/

The 3DS has a fantastic library but a good chunk of it is very difficult to obtain these days—either because it was only available digitally, or because prices for used physical copies are unreasonable.

It’s sad that Nintendo don’t give a shit about preservation past their ability to sell old games over and over, but if I can no longer give the creator money for a game I’m of the opinion that largely absolves any immorality of piracy.
Obama's Trauma Team (2014)
Why is that the smallest possible unit? It may not be especially practical, but it's certainly possible to break Amazon up by retail product category (one company for books, one for kitchenware, etc).
Worked at one. 48 hours of diesel at the location I was at with a supply contract that had stiff penalties for letting the tanks run dry. Besides annual maintenance the contract prints money for the provider in between events. Registers worked without internet but satellite backup to terrestrial internet obviates that problem in most scenarios except a carrington event. Only the gm and another manager could reorder or run a register on paper but that likely would never be needed with their other preventative measures. Is also easy to train someone once you have one person that knows how. Pay and conditions sucked but it is nice to know that the company takes their responsibility to the community seriously.
There should be counterincentives to corporate gigantism and conglomeration. Its as simple as that.

A smartly organized market economy does not wait for oligopolies to wreak havoc before it resorts to costly and slow litigation.
Current LLMs clearly have much coarser models of the world than humans do. Their training data do not include as many modalities and training data with spatiotemporal dimensions are inadequate.

Up and coming multimodal models are changing this.
Do you still find this true when taking type aliases into account?
Your recommendation is to stick to a pathological implementation where every page fault results in the equivalent of doing a Java GC run? All independent of the actual memory pressure?

This isn't even about the exact limit, this implementation just makes no sense. Add a hysteresis at least because running this on every page fault is guaranteed to cause a lot of CPU load while not returning very much to the system.
Show HN: Sqinn-Go is a Golang library for accessing SQLite databases in pure Go
You're linking to a partisan hit piece from a biased news source desperately trying to create a racial narrative out of standard faire politics, because that's what sells clicks to people that get worked up about such things even in the absence of real substance.
How possible is it to find cheaper options even if someone wanted to do so? It's nearly impossible to get healthcare providers to commit to a price.
Hmm, I think you’re right! Apologies! And now off to check my firewall rules!
> Is Shuttle Secure?

> We build and deploy every project in its own container. This gives you safe isolation from other users and all the other projects that are owned by your account.

So that's a "no". Containers are not strong security boundaries. Probably good enough between projects owned by your own account, but definitely not for between other users.
It depends on the kind of customization and its complexity.

If I feel the customization may be useful for others, then I file a pull request against the upstream project. I strongly think that upstreaming your change is a good practice, and that it should be considered the default.

If the upstream maintainers reject my change, or if I ended up not proposing it upstream for some reason, then I usually do one of the following:

1. I fork the original package and publish it under a new name or in another namespace with my customizations included. Then I keep track of upstream releases by subscribing to a release feed of the original package (e.g. if they use GitHub releases, I append `.atom` to the URL of the GitHub release page). I then port my customization forward on upstream releases. Or,

2. if it’s a Javascript package, I use `yarn patch`, see [1]. Whenever I bump the dependency, I bump/port the patch, too. Or,

3. if all else fails, I think I might vendor the library into my source tree as a last resort. But I’ve never actually done that.

[1]: https://news.ycombinator.com/item?id=37633559
> If I do a run of of my book, and it sells out, I don't think it becomes open season on duplicating it digitally

Nobody is asking for that. We only want it to become open season on duplicating it digitally if you choose not to do any further runs of it.
On cars with an electronic handbrake, do they have a way to apply the brakes while the car is moving?

Also while it's not mentioned in this article, The Guardian's article says "MG Motor UK has been urgently trying to make contact with Mr Morrison so that his vehicle can be fully inspected by our engineering team." It does seem a bit suspect that he's happy to chat with journos and pull faces in front of photographers, but not to chat with MG.
Show HN: Vanilla CSS Tailwind alternative in 16 lines
I'm curious why robots are generally very slow. Is it because of the actuators being slow?
So you don't even know what the article is discussing. Amazon is killing competition and increasing costs to consumers.
Ask HN: As an IT person, what do you like and dislike about cars?
What do you like about it relative to alternatives? How fast is it?
The Math Behind Colors
There's been considerable convergence on this. Most languages now have some degree of type inference for statements now. Even C++ has "auto". That substantially reduced the amount of type boilerplate in code. Remember having to write out long iterator types in C++ "for" statements? We're past that.

As for function declarations and structure fields, that's where you need type information to read the code. Once a program gets beyond a few hundred lines or beyond one developer, some amount of annotation is essential.

The main objections come from Python and Javascript users, of course. Python retrofitted a very strange advisory typing system, and Javascript retrofitted TypeScript. Both are bolt-on type systems and are used in mixed typed/untyped environments. That is painful.

LISP also got a type system retrofit decades ago, with "flavors" and the Common LISP Object System, and that was ugly, too. The lesson here is that retrofitting a type system creates a mess.
The parking brake is a completely separate system (required by law to be separate I'm many cases) that is independent of the hydraulics, ABS, etc. It's literally a cable attached to a lever, or to a motor (the actuator) that applies a shoe in a drum (or in some cases a pad to a rotor).
> coherent model of the data generating process -- a world model.

I'd never seen a definition of world model but this seems deficient in several ways because it does not mention anything about abstraction and logical reasoning.
100% this. Developer experience in a language is a so much bigger question than if it has static types or not.
Yeah that's not the case lol. ann's can model any function even non linear ones.
I know I should respect the hustle, but hard to respect a middleman adding 0 value to the process.

I also love how they softened his side hustle by fitting "helping make tickets more affordable" in the same sentence where he says he resells them at a higher markup.
> So basically, stop using smartphones, because it's fucking ridiculous to drop hundreds of dollars every 4 years on a device that is virtually the same thing as your old one. This is a huge joke, and Google and Apple need to do better or stop milking us.

I mean, you're literally posting this complaint on a thread about a phone that is now legally bound to receive seven years of updates.
This may be a very ignorant question, but is anyone using Java for new projects these days? Or are most of the projects legacy projects? I've not heard of anyone electing to use it anywhere as their first choice.
The comment you're replying to is criticizing dynamic typing here, not static typing.
curl 8.4.0 containing high severity issue fix announced for October 11th
> What I'm wondering is why we can't use a similar system as SML to infer the types.

We can and do! Use SML!

People just don't find out about the good type systems because the market is crowded out by mainstream shit.

And people write pieces about how good this shit is: "I was going to add an Int to a String but the compiler stopped me! Less [sic] bugs!". With arguments like that, why would you switch camps?

Or sometimes you get fed shit and get told it's inference: "I can replace the first word on the line with 'var'!".

So what are the downsides?

Inference doesn't play well with inheritance or mutability.

If you read Effective Java and see the points about avoiding mutation and inheritance, then these downsides may very well seem like upsides to you.

Why did you stop coding in SML?
If they had pointed to their ad, I may have known that at the time of writing. However, cover letters are required almost universally. Prospective employees know this, and are collectively responding to bullshit-questions with bullshit-answers. Perhaps the tide is turning, but this single small employer's opinion is not representative of the industry.
Interesting. Are you sure it actually uses the parking brake though? Do you like hear the "screw motor" (if it is one of those).
Nexus phones were what are now Pixels
It's amazing how quickly I recognized eBay descending into this sort of stuff from its inception. Maybe Amazon did so quickly too, but it's so obviously scummy that even as a teenager I got this impression. Kudos to you for going the extra mile
Introducing TextTransformerPro.com: Your Ultimate Text Processing Companion

Are you tired of grappling with messy text data? Look no further than TextTransformerPro.com, your new online service designed to simplify and supercharge your text processing tasks. Whether you're a coder, data scientist, or content creator, this platform is your one-stop solution for effortlessly handling text data.
I know that sometimes these lawsuits can take awhile but scheduling something 3 years away seems excessive. It feels like discovery can take months, but years feels like a very long time here especially since this is something that is actively still ongoing and damaging to the victims
Because you run into the issue of "unscrambling the eggs". If Amazon is not organized by retail product category (and I would assume it is largely not), then it will be very difficult to split the company in that way. Courts really aren't in the business of restructuring companies and the last thing you want is for the new baby companies to fail because the restructuring went poorly.

Which employees go where, who gets what IP, what happens to all the underlying website/physical infrastructure? A "3rd party marketplace" unit is already likely smaller than is feasible for a court to oversee. By comparison, it would be a lot easier to split Amazon into "AWS" and "not-AWS" because the company is already organized that way.
Location: Oslo, Norway

Remote: Yes, preferred

Willing to relocate: Maybe

Technologies: machine learning, deep learning, Python, PyTorch, NumPy/Pandas, flask, SQL, Docker, Rust

Industries/domain expertise: PhD in mathematics (statistical methods/modeling, topological data analysis, representation theory), master's theses in finance and neuroscience, application of machine learning/deep learning to banking/finance for risk evaluation and fraud prediction

Résumé/CV: available on request

Expertise in data science and development of ML/DL models across domains (in banking/finance, for domain-specific image analysis and for neuroscience); 6+ years professionally working with Python and machine learning

I'm actively exploring remote opportunities where I can apply my unique combination of skills coming from a math and developer background

Open to freelance/contract work.

E-mail: hn [at-symbol] vixe [dot] re
TS is an interesting example to pick when trying to argue that types are better. You have all the same downsides people pick on when arguing against strong, static typing, but since the type system isn't sound you still can't rely on the input to a function being the type you expect (and the problem is worse anywhere you inevitably interact at least a little with the JS world outside your TS bubble).

At best it's a form of documentation that enables some simple linting rules and a bit of jump-to-definition magic. Like, that's a benefit (mostly -- I tend to think that type signatures implying more guarantees than they provide is a recipe for inadvertently relying on falsehoods), but it's not as clear-cut of a win as you see in other statics/dynamic tradeoffs.
I think this is completely false. It completely breaks down as soon as you get into your first refactoring that is a bit larger than completely trivial. Typically the mess one ends up is one or more of the following. (1) Nothing is refactored because people do not dare to do it. (2) Not just some but most of the uncommon code paths are broken. (3) Tools that are used to interact with a running application are regularly in a broken state. You want to prevent these problems with 100% test coverage. As such this may be a laudable goal on occasion but I do notice that the code described in (2) and (3) are highly non-trivial to cover 100%. I also have to wonder what mythical developer is does not have the discipline to use static typing but does have the discipline to attain 100% code coverage. I first want to see such a developer before I believe in his/her existence.
Post about pen plotter without video. Hmm, I feel cheated.

Random video of old school pen plotter in action: https://www.youtube.com/watch?v=3Cd3GsZlOBg

My father still fondly talks about how the crispness of a true pen plot was never really matched by modern printers.

Edit: he has them on a second page: https://szymonkaliski.com/projects/diy-pen-plotter Not as fast as the 1983 version though :)
The rise of the novice coder: Can AI turn every employee into a developer?
I doubt anyone is arguing that our bash scripts should be typed, or our quick "remove_currency_from_bank_csv.py" must be statically typed.

The article puts a few cases forward. What the article is discussing, however, is the majority of software. Built in varying teams. Over long periods of time. Large software, complex software.
I can't get the .torrent file to work in my client. Can anyone give me a magnet link for it?

I need the magazine ISSNs for my magazine encyclopedia.

edit: got the .torrent working in qTorrent
Yeah, I had a similar experience with Chroma DB. On paper, it checked all my boxes. But yea, it's alpha software with the first non-prerelease version only coming out in July 2023 (so it's 3 months old).

I ran into some dumb issues during install like the SQLite version being incorrect, and there wasn't much guidance on how to fix these problems, so gave up after struggling for a few hours. Switched to PGVector which was much simpler to setup. I hope Chroma DB improves, but I wouldn't recommend it for now.
> Just get the newer compiler to build the newer code.

I think part of the problem is that this is backwards to how people coming from other traditional languages (like C, or C++) think.

With those, you deliberately choose your target compiler in a way to maximise who can build your software. Telling all your users "just get the newer compiler" is rude. If you can reasonably target a 20-year old version of the compiler, so that users on systems who can't upgrade their compiler for reasons you have no control over can still build and use your software, then that's a trade-off worth considering.

Note that you don't always have to choose that, but you should consider it. And when you do decide to move from, say, C89 to C99 (or - gasp - C11), that is a carefully considered decision. It's not just ooh, shiny.

You don't always know who all your users are, or why they may not have the same flexibility as you. But if you want your software to be installed on 10 billion devices, that's the sort of thing you have to consider.

https://daniel.haxx.se/blog/2022/11/17/considering-c99-for-c...

https://curl.se/docs/faq.html#How_many_are_using_curl
The "hiatus" was bullshit in 2013 and it's still bullshit. See https://www.ipcc.ch/report/sixth-assessment-report-working-g...

So much for the integrity of the Daily Mail and the denier who posted this.
It depends on what kind of information you need. If i need an authoritative source then LLMs cannot really replace search currently. If they improve however it could become the replacement. For example if you say find me authoritative links the AI could run the search, check the results and give your best ones. It does not do that currently but it potentially could in the future. Now this does not really replace the need for google as a search engine. It might mean that a lot of google traffic would suddenly come from OpenAI. That would probably impact googles bottom line. If the traffic gets big enough they will block it and ask for payment. Or they might even ask OpenAI to show their Ads to the user.

If you just want a quick answer then LLM can actually suffice (if you trust the answer and dont need to check). Like for example how many eggs do i need for my cake?
The first AppleTV was released in 2007. The first Roku in 2008.

As far as Amazon copying others as a marketplace owner, ever heard of the Kirkland’s brand? Store brands have been around forever.
Pixel 3:

https://browser.geekbench.com/v6/cpu/2900039

Aside from all the other problems a genuine pixel 3 (or iPhone XS) battery is bellow 3000 mah, so like replacing your redmi battery with a defective one.
> How is Apple to blame for non-replaceable batteries?

How quickly we forget history. I'm not going to say they were the absolute first to do this as I'm not doing a full survey of 2007 phones, but before that (a) there was not a single phone I or my friends had that didn't have a simply replaceable battery and (b) there was a ton of conversation and press when the iPhone was first released about how unique the decision was to have a glued-in battery here.

For contrast, here are instructions for replacing the battery on the famous Nokia 3310 https://devices.vodafone.com.au/nokia/3310-2017-proprietary-....

Let's be real here: if having difficult-to-replace batteries was a money loser for Apple and other manufacturers, they would fix the situation in a heartbeat - it's not like this is a hard problem. The only reason they do this is because of desired planned obsolescence - tons of people will think "Oh, getting the battery changed is such a hassle, might as well get a new phone."

Again, essentially every consumer electronic device pre-2007 (except maybe some Mac laptops?) had easily-replaceable batteries. Convincing people that using glued-in batteries was a necessary design change, instead of a corporate decision to make more money, was a real coup for corporate marketing.
What is the final resulting accuracy?
When I hit ctrl+save, the code should be instantly ready to test, less than 200ms. Waiting for 30 seconds to see code is an ETERNITY to people that code fast, 1k lines per day. I have been on teams that wait 5m to test code, what a waste. Fast feedback loops in code are critical, just like design, or anything important. Types seem like some weird religion, the people that use them cannot be talked out of it.
Show HN: Pronounce Names from Around the World