skysight-inc/HackerNews huggingface dataset:
Sorry but this is not completely correct. Many expert bodybuilders use a variety of machines to train each muscle group.

Power lifters, however, tend to focus on the compound movements and therefore probably need less equipment.
How many people were hurt here?
You will find that if you go at the times I go, most of these things are not a problem. It's usually only the serious, respectful people who show up at that time. Once I went to the gym around 5pm and OMG, it was the first time ever I felt like why am I here. Never happened again !
> its still better than

* is not worse than
Two different variants and two different kind of failures.
Aliveness: Reframing Productivity
Looks really cool, but I'm not exactly sure why it doesn't just use Sqlite.

On the other hand, I suppose it's an opportunity to practice MySQL if you expect to need it later for pro sysadmin work.
I think it explains more about one's world view than anything else.
>I appreciate your dedication to reminding us that your original comment was posted without any research or thought

I, on the other hand, don't appreciate the ad hominem. What happened, have manners gone out of style?

Also, what exactly fault do you find with my original comment: that Go isn't really a player in scientific computing. Does your "research or though" suggest otherwise?

>99% of Go users don't need an FFI story at all. They can choose a compiler on different merits.

Users of X don't need Y is a self-fullfilling prophecy when X doesn't offer Y. Languages without Y don't tend to attract users who need Y.

We're also talking about users doing scientific computing here, where the vast majority does need an FFI story.

>gc is not ideally suited to FFI. But Go offers compilers that are. This is not a Go problem. Go provides solutions. What you speak of is only a gc thing.

And gc is 99% of what people understand and use as Go - not gccgo. Unless gc has a good support for certain features, scientific computing ain't gonna happen.

People aren't going to heavily invest in building scientific programming libs interop with Go, when those would just work fast enough in a different less used go compiler as opposed to the mainstream one.

>What story do you have for us next? That your neighbourhood restaurant, with a full menu, has no hope because the one dish you tried wasn't to your existing taste – not having it occur to you that other items on the menu might be exactly what you are looking for?

Yeah, because a different version of a compiler doesn't come with different maturity, different technical tradeoffs, different community using it, different support story, and so on, it's just like "picking another item from a menu".

If that's your understanding of the situation, I can see how your argument would make sense in your mind ("just change the compiler, it's easy").

Using another language as an example: If CPython didn't have a good interop story with scientific libraries, even if PyPy did, "Python" would have gone nowhere in that domain.

And people who can't understand this, would talk all day getting blue in the face about how "it's not a Python problem, it's a CPython problem", as if that would change anything.
The explanation that, "people have nowhere better to invest/go" is my favorite explanation for who the US will stay strong. It comes off to me as very authoritarian and almost a threat.
It would hurt the brand to cheat the sat-nav based range, it would mean the car wouldn’t make it to a charger when it said it would. You’d have a lot of unhappy customers.

Think of the sat-nav range as closed-loop and the other testing based ranges as open-loop.
Sounds like more redundant thermostats and median filtering is the solution, not removing all and melting your engine.
> These days, I’m much less worried about this admission, in part because the alternative I have gravitated towards has given me greater personal satisfaction and, I hope, insights: history.

We have been taught the history of colonialism in school, for many, many years. I don't think I understood what colonialism was, or what it was like to be colonized. Until I read fiction in my adult life. You could know the historical facts by heart, but to get a sense of what something was like from a subjective point of view (which is also a kind of knowledge), I don't think that fiction and history are comparable.

I also knew some history about slavery, I also watched movies about it, I thought I knew the salient points about slavery, until I recently read Frederic Douglass, the narrative of an escapee from slavery[1]. Yes, it's not fiction, but I got some insight into what it was like to be a slave, from within, and I don't think I would have ever gotten this kind of insight through history, facts, whatnot.

The author clearly underestimates the power of fiction, even as a vehicle of knowledge.

[1] https://en.wikipedia.org/wiki/Narrative_of_the_Life_of_Frede...
Operator overloading leads to less readable, maintainable code IMHO, because you have to go off and figure out if the operator means a special thing in a given context.

Certainly adds to complexity in C++.
Need Your Thoughts: How Can Logistics Go Green?
Hey everyone! I'm a student working on a project about green logistics. Need your help! Do logistics companies prefer all-in-one green solutions? What makes a provider attractive to them? Share your thoughts! #GreenFlee
I don't know how any of those examples are supposed to help in this situation.

You have exactly two relevant phone infrastructures in the Western World. One is pretty open and the other is locked. Usually it doesn't cause many problems besides envy. People can still talk with each other. It works quite well all over the planet because of third party commutation software like Whatsapp, Facebook, etc.

However, on the locked ones biggest market there is a special situation where the fact that third party software is not that popular. This situation grew out of historical reasons and has created a toxic problem which divides the whole country almost in half. None of your examples above is so widespread and creates such a huge divide.

So what is it you can do about it as a company? You could allow for interoperability within the established communication methods your customers use. Or you could just ignore the problem and be happy about all those customers who have to buy your expensive devices and services only because they don't want to be outcasts in their class, in dating, at work, etc.

The decision Apple made here shows their attitude towards their customers and their potential customers. An attitude towards the society at large, actually. Looking at it from outside the US-bubble it's quite shocking and pretty much disgusting. I wonder how people working there are not ashamed of themselves for keeping such a problem up.
Those planes are approved at multiple levels.
If you cannot model using decent code is it worth writing models at all? What if bugs mean the model is simply wrong?

It has consequences too. There has been a lot of argument about how much impact the poor code quality of the Imperial college covid epidemiology model (which was the basis of British government policy during the pandemic) had on its accuracy. I do not know how bad it was, but it cannot be good the code was bad.
That narrative is idiotic, sure pirates might buy stolen drives, same as gangs use knives. Stopping one won't affect the other.
If we are adding a copilot key the keyboards also need additional hallucination warning LEDs.
IIRC the Blackberry Messaging app (BBM) was cross-platform.
Are they following agile or what?
> lack of effective oversight

Regulators getting cozy with the people they're supposed to regulate happens in every industry, in every country, and... understandably so. Those are people who have the same expertise, same training, who work together all their life.

It may be one of the most difficult problems to solve.
If toxicity based upon bubble shame becomes a norm. You should actually be ashamed of yourself as a company, but I guess these days shame came out of fashion.
Android was already using Java and Dalvik (their JVM variant) at that point, so switching to Go would have been a massive undertaking.
I wish we communicated the intent of the “best practice” instead of the practice itself.
Great read and a trip down memory lane for me as I cut my teeth being a field engineer for a small IT support company in London for 2 years was back in 2005.
Jason has posted elsewhere in this post, but textfiles.com is a safe bet for a future home for nearly any kind of log of that sort.
I would think it is the same type of failure. Management failure.
Tangentially related:

"The case of the 500-mile email"

https://news.ycombinator.com/item?id=9338708
cute, good job.
some color indication on the cards could be nice to make it more visually obvious whether its day or night
No, it needs hardware support for that. It needs another level of virtualized MMU, which Apple didn’t build in. That might come with the M4 generation only.
In the same domain I used for years timebuddy https://www.worldtimebuddy.com/
>Writing clean and maintainable code should be the best practice and writing obfuscated code for performance and security should be reserved for "few specialised cases"

Except, we can (fairly objectively) reason about performance and security, while 'clean code' and 'maintainability' are arbitrary, with vague guidelines at best.

Throwing out those first characteristics in name of the latter ones is just irrational.

(Not to even mention that performant and safe code still can be 'clean')
passenger boats are way overdue for a come back.

don't even mention nasty cruises which only cover coastal routes, like some paleolithic dingy.
Hey that’s a really cool idea. I get those sales pitches all the time too. Hate wasting so much time checking them.

We can plug into gmail and make it happen!
Yes, some people read Clean Code and think every file should have less than 20 lines. I recently inherited a React project that has all single-use utility functions, graphql queries and component types extracted out to different files. Having to edit five+ files to change things in one component is a nightmare experience and slows down changes a lot.
Agreed! Should be quick to add.
It is possible to cryptographically attest to attributes like age without revealing identity.

I worked on a privacy preserving system that did this among other things. Third parties who received an attestation of some property could verify it.

To be fully private, a bit more is required. Crucially, each time an attestation is provided it is made unlinkable to previous times it may have been provided. So the third party only knows the attestation they have just received is valid, but not that it is the same unknown person they saw yesterday.
"Deliberately" is a rather strong way to say "accidentally". When multiple different totally independent teams manage to subtly break things, I think you have to start questioning the tool rather than the teams.

Like, I don't know, maybe the problem was caused by a dependency they were using rather than their own build scripts. How do you know, how do you fix it? What are you supposed to do, not use dependencies?
The pilots have nothing to worry about. They're locked onto the cockpit.

You'll forgive me if I find your assertion strains credulity.
We naïvely bought a book of classic German fairy tales and somehow no such stories appear
I think its a para-social thing. We are not build to see somebody everyday in a certain context and only passively interact with them. This crosses a couple of wires I think.

I have similar desires to not meet them but its mostly because I do not care that much and they probably have enough randos bothering them. I would probably dive under the table as well as in the article :)
American home ownership is so loaded with plantation era subtle subjugation in the form of linguistic convention. If master bedroom were the worst it would get attention.

I switched to originating new repos as main instead of master personally, reinforcing the concept of “commuting to” or code “being committed” to “master”, seems diametrically opposed to progress.
> at 65 years old stood on the tarmac with a machine gun until a plane’s hijackers surrendered.

That's a funny story. In fact, too funny and hardly believable...

According to a NYT article from the time of these events, the 4 hijackers accepted to release their hostages after a promise that they would get a plane back to their country. The hostages were released as planned, but then the hijackers where met by 200 armed soldiers and the President, himself armed with a submachine gun. Two of the hijackers were killed.
https://www.nytimes.com/1971/12/19/archives/president-says-n...

The tale where an old man with a machine-gun forces hijackers to surrender is more striking. Who cares if it seems impossible? Some newspapers (LA Times, Time) even propagated this, and now it's in Wikipedia-en, but not the Spanish version.

I think the NYT is a better source and its story is much more plausible. But the showdown is less funny and flattering. The President broke his promise. He did confront the hijackers, but he was protected by 200 soldiers, and the 4 hijackers had already surrendered.
Every Time Zone – Check times across the world
See also: https://www.visidata.org/
> Many programmers have no real substance in their work – the job is trivial – so they have too much time on their hands, which they use to dwell on "API design" and thus monstrosities are born.

Definitely getting this vibe from modern frameworks and design patterns.

I want to like SwiftUI, but the WYSIWYG editor doesn't even work for the default projects for me. Storyboards were great for creating everything UI except tables and collections, where it was still functional just meh. The reactive UI in SwiftUI… mostly works, but sometimes doesn't, and when it doesn't I can't debug it because it's a magic black box; you can get similar results with a small amount of extra code in UIKit { didSet } on your model property and each input control, and while boilerplate isn't great, it's better than magic which only works 98% of the time.

I'm trying things in JS in my spare time, no libraries or frameworks, and it's easier and faster than getting anything done in XCode. And that's despite the Swift language itself being one I prefer over JS, and that I'm doing the development in BBEdit which is a text editor not a full IDE.

But this isn't just about Apple; the reason I'm not using any JS framework and libraries is that every single talk I've seen about web development has exactly the same problem, piling on layers of stuff to fill in the gaps missed (or created) by the previous layer of abstraction.
I kind of agree that the "reset to now" button should be in the global context, as resetting each timezone to now separately doesn't make as much sense.
> I'm not sure why he didn't take the $500 and set up the software on the little punk's phone.

Because you shouldn't spy on people?
Mine was

> As smartphones became more of a thing, the number of "please spy on my teen" requests exploded. These varied from installing basically spyware on their kids laptops to attempting to install early MDM software on the kids iPhones. I was always uncomfortable with these jobs, in large part because the teens were extremely mean to me. One girl waited until her mom left the room to casually turn to me and say "I will pay you $500 to lie to my mom and say you set this up".

> I was offended that this 15 year old thought she could buy me, in large part because she was correct. I took the $500 and told the mom the tracking software was all set up. She nodded and told me she would check that it was working and "call me back if it wasn't". I knew she was never going to check, so that part didn't spook me. I just hoped the kid didn't get kidnapped or something and I would end up on the evening news. But I was also a little short that month for rent so what can you do.
It’s not novel so much as an invitation to do the same.
Idea for a startup, a website that sells plane tickets exclusively avoiding Boeing planes. You have a customer waiting.
But at some point you HAVE to be able to look at the program from above.
If you abandon the hope of understanding the code in the bigger scope, how can you ever meaningfully modify it? (Ie add a big feature and not just tweak some small parameters)
I disagree, I want them shown in the order I add them, not in order of how far from the UK they are.
Oooh, that's a nice idea.
Thanks for fun )))
You're inviting people to go looking at people like Mark Oliphant, Brian Schmidt, Howard Florey, Fred Banting, Lord Thompson of Kelvin, Rutherford...
> bash (tons of other deps)

already excludes most modems and iot. :(

probably need a rewrite in sh and dropbear
> It's bordering on paranoia :)

FWIW/FYI... as someone who has collaborated extensively in the "Hwaci ecosystem," for lack of a better term (projects stemming from Richard Hipp and his company (Hwaci)), i can elaborate a bit on that...

It's not about security in the conventional computing sense, but more about _supply-chain security_. Any third-party components can become unmaintained or break in incompatible ways at any time. The Hwaci ecosystem has a strong culture of avoiding third-party-dependencies, stemming from/related to Richard's definition of freedom: "freedom is being able to take care of yourself," i.e. not depending on others to take care of you. It's important to Richard, and is therefore a part of his projects' cultures, that those who maintain the project are capable of continuing to do so. It's not always feasible to take over maintenance of upstream third-party code, or port away from it, if it suddenly becomes unmaintained. Similarly, it is not always feasible to adapt one's own code to incompatible changes made in upstream third-party code. Avoiding upstream dependencies, despite the obvious annoyance of having to re-invent the wheel at times, inherently gives a developer more freedom over the direction of their own projects. All projects within the Hwaci ecosystem share the trait that they eschew third-party dependencies unless they are (A) unavoidable, (B) non-trivial or non-sensible to reimplement in some minimal form, and (C) ubiquitous (zlib, libssl, and tcl being the counter-examples which most readily come to mind).

That's the short and the long of it.
This is the battle I am currently fighting.

Specifically when working with numbers (something scientists do), i feel it is more important to know the numbers and have an intuition of what is important to get right and what is less important. Rather than spreading unit tests and the following abstractions all over the place.

But scientists can create a hot mess too. This is when they don't care about the code enough to minify it. I.e. reducing the code to what is necessary.

Number of lines of code matter.

So the perfect blend here is not necessarily the person that follows all engineering practices. But the person has the domain knowledge but that knows enough about software practices to be able to write concise code.

If you are either missing out on the domain knowledge - or the ability to reduce the code - then it will derail.

Shipping the notebook to engineering department will not be the solution. They will break the code into pieces, follow best practices but miss out on the important.

And another aspect of this practice is that if someone finds a problem, the scientist will not be able to modify or re-run the engineered version of the notebook.
Can $500M Save This Glacier?
This struck me like a Medicare benefits review commercial. I think those are also a bit more substantive. ;)
> That whole family of projects avoids third-party dependencies where at all possible for reasons too detailed to type out one-handed on a mobile device.

... but which has since been elaborated on in <https://news.ycombinator.com/item?id=38890382>.
Mixtral is only 32 ELO ahead of the best 7B model on that leaderboard, although I suspect that might be understating the difference.
> Which is not the same as what you may have actually done to change old file into new one.

I’ve seen this with methods: I add a method, so I expect to see the whole new method in the diff. But actually the diff looks as if I’ve inserted something just before the closing brace of the existing method above the new one.

I’ve learned to detect this when reading diffs but a nice display would be, err, nice.
They

Who are these people, really? I mean, I was that for a rather brief period of like a year, somewhere 3-4 years into programming IIRC. I met others like it. But in the end people seem to learn and grow out of it, and rather quickly so, because it becomes clear what the issues are quickly. Really good learning by mistake though, wouldn't have wanted to miss out on it.

mantra

That's imo just another mistake to make: wrapping a rather strict and narrowly scoped principle in a paradigm-like-must-be-followed mantra hurts the right-tool-for-the-job idea, which feels vastly superior.

Firstly the idea that unmaintainable code is necessarily an issue is already wrong to start with, in my book. Obviously it's not ideal and where appropriate - meaning nearly always - should be avoided at pretty much all cost, but I have enough examples where it does not matter at all. As in: code which hasn't been touched in 20 years and probably won't ever be touched. Does it look like a nightmare? Yes. Does it work correctly? Yes. Does it need changing? No. So, is it an issue where spending time (or having spent time) on it would make anything other than the programmer's peace of mind (well, or ego perhaps) better? Clear no.

Secondly: of course I get where you're going with such definitions but it again lacks the very much needed nuancing. I can write unmaintainable code in one file but where you need to change 20 different locations. You could than claim that your mantra still applies because the code should have been split over 20 files, but yeah, that's what you get with mantras :) Likewise depending on the feature it's perfectly possible many files have to be changed but that doesn't necessariy mean the code is hard to maintain. Could try to claim that it wasn't very well architected to start with, maybe, but welcome in the real world where not everything can be thought of from the very start except in small toy applications.
I guess the question I would have is: to what degree is this happening in the US versus other places like Europe or China, and what can we learn by examining this in those places.
Facebook? Have they changed the llama license?
Thanks, seems funny, did you try it already?
Kayak already has an aircraft filter, the many other flight comparison sites could easily add the same.
visidata is awesome. It also supports a bunch of other file formats such as excel sheets.
Agreed.

I find C easier to understand than the algebra of other languages such as Haskell, Ocaml, Rust because of how C statements correspond to assembly.

Memory is just a big grid of numbered locations and computing is logistics between grid locations. Execution is transition between memory locations.

LEAQ or "&" (C addressof) is an address calculation or LEAQ for one of those grid locations.
Very neat. Reminds me of the Overlap app by Moleskine Studio: https://moleskinestudio.com/support/overlap/introduction/ove...

Great UX but only available as an app. You have the advantage of being on any platform and able to create share links.
Number one reason is lack of meaningful competition (political buying decision Boeing vs Airbus) and industry monopolization. In the 1960s there were Douglas, Convair, Lockheed, Boeing domestically
I don't use the Internet without strict ad blocking, so that's a no for me.
Show HN: FlaskyLMS- Simple Leave Management Tool with GCal Support, Email Notifs
A simple leave management tool that I built for myself a while ago. Now sharing on GitHub. Not the most pretty looking and lacks many bells and whistles but still gets the main job done xD