skysight-inc/HackerNews huggingface dataset:
As a long time daily biker I don't understand the trend of heftier more powerful ebikes. Instead of bulking a bike up to me it makes more sense to slim cars down.

I've been trying to find tiny electric two seater cars, but I've been disappointed in the lack of anything in the US, they're more available in europe and Japan.

Actually now that I typed this comment out I think I understand the trend of heftier ebikes, it's a way to skirt the regulations around making a "street legal" vehicle, which is what prevents any innovation in the <$10k tiny car segment.
Netscape should name it Netscript
Earthworks at the Leaning Toothpick of Babble
What does KF have to do with HN?
You are missing the point completely.

The IKEA effect is not "self assembly", the IKEA effect is "I think of this piece of furniture more highly because I assembled it myself". The IKEA effect compares how people feel about the same piece of furniture when they've assembled it themselves vs when someone else did it.
Part of the issues were due to an unforeseen pandemic that messed up the supply chains and increased prices drastically. However keeping the plant running may not have been feasible. There's some coal plants on Maui were parts suppliers shutdown or simply don't produce spares anymore. The energy producer there is faced at trying to get custom fabricated parts and hoping they work or building a whole new plant to provide interim power. A lot of these projects were planned years in advance and major disruptions (like a global pandemic) can wreak havoc on plans.
People are already tired, but there’s simply not enough of them to effect any change. Especially when opposing large, well funded lobbies that are de facto writing the relevant laws in the US and EU.

I don’t know how we’re going to be able to change this. I’ve voted for parties that are the most outspoken on this issue all my life. But somehow this never makes it into any actual policy.

I’ve even on multiple occasions called my representatives as parts of grass roots lobbies against new trade agreements or laws that would set us back even further. But even when such grass roots campaigns were successful, the same proposal would just return at most a few years later and the grass roots oppositions would get tired of trying to stop them.

What else can we do?
I switched to an RSS reader recently and was shocked to find that every site I was interested in, large and small, had an RSS feed. I guess I was lucky.
I'm waiting on Verse a new scripting language for UE by Epic called Verse. A Twitter thread posited it may be called Unreal Verse ;) It is supposedly inspired by Smalltalk and has some Lispy goodness. Can't wait. I played with Rust, and I think it is fine, but too much overhead for me to get productive with it. But that's just me. I click more with Lisp and terse languages (J, APL, Scheme, etc.). So many options to be grateful for!
I currently have a Toyota hybrid that is slowly reverting to an ICE-only after 8 years of ownership. Unless there's some mechanism in place to prolong the life of electric cars beyond the limits of their battery, I can see there'll be a lot of holdouts (young people, less well off etc.).

Regulation in the big markets such as the US and Europe to enforce a cost-effective approach to battery replacement seems essential to me. Otherwise, design will go the way of ever slimmer phones.
Also investing in a branch predictor when the intended workload doesn't seem at all scalar is a confusing choice to me. Also the 362 F16 TFLOPs sounds super impressive, except the memory bandwidth is I think 800 GB/s (or is it 5 times that? Or effectively less than that if data has to be passed along multiple hops? I'm a bit confused), which means having to do 1000 ops (or 200? or more?) on each 16 bit value loaded in. Maybe you could do that, but it feels like you'd probably end up bandwidth bound most of the time.
Feel free to do this, nobody will join you so the spam will be virtually nonexistent!
> if something like this is released as open source, the author will make a grand total of jack shit off of it because people will just grab the source and walk away without any kind of compensation to the author

I don't see how this is anything but unfortunate (okay, it's also untrue [krita, RedHat], but bear with me for the sake of the argument).

> we pay them for it. [...] But if a software engineer makes software that has clear value... we lament that it's not free?

Now we're getting somewhere: we lament that it's not free even when we pay them for it. I would rejoice if we paid them to make the software free.
Even at current prices he has millions of dollars in stock. People think in illogical ways, but I feel the reason must have been more than just financial.
Recycling Clothes: What Is 'Circulose' and Is It Sustainable?
A lot of people giving their opinion about TDD, but not many actually answering your question.

The answer depends on your approach. You can go outside-in (top-down) or inside-out (bottom-up). The one you use is a matter of taste. A lot of people find outside-in easier, but inside-out can be a bit faster if you have a good sense of how your system will fit together.

To take an outside-in approach, start at the top level of your application. Possible just under the UI, because UIs can be hard to test. (If the UI isn’t tested, make it do as little work as possible, and have it just forward to the tested code to do real work.)

Test-drive a module, class, or method in that top layer. The smaller the better. If there’s something complicated that should be handled by another module/class/function/method, make the module/function/etc., but just hardcode one answer. Make a note of the things you hardcode.

When you’ve finished TDDing your first thing, look at your notes and choose something that you hardcoded. TDD that in the same way. Repeat recursively until the application works. Focus on getting to a working but incomplete application as soon as possible, by working depth-first instead of breadth-first.

Once you have a working but incomplete application—a “walking skeleton”—think of a feature you’re missing and add it in the same way. Continue until the application is done. Remember to look for opportunities to improve the design and refactor as you go.

Inside-out is very similar, except that you do the depth-first recursion in your head, mentally, and don’t write any code until you get to the leaves of the recursion tree. You test-drive the leaf, then test-drive its caller, etc., until you get to the top. It takes more experience, more thinking about design during TDD, and more willingness to refactor.

I have videos on my site if you’d like more. Start with this series:

https://www.jamesshore.com/v2/projects/lunch-and-learn
It does no such thing, that’s absurd. See carpenter v. United States (among many, many others).
Renault Twizy was quite popular for short distances here in Europe.
Nothing should be going 30mph on pedestrian infrastructure. If you want to go 30mph, you're going on real roads with real cars. I own an eBike, love it, and use it to commute, but 20mph is already too much around pedestrians.
realistic daydream != practical idea

realistic daydream is like an oxymoron because it conveys the idea that it is unreasonable for most people, but practical for him.
Unlawful content gets posted to Facebook, Twitter, YouTube, Reddit, etc. all the time. We don't deplatform all of them just because there was a window of time in which it was posted but not yet removed.
That's what he means.
Sizeable companies juggle hundreds of lawsuits simultaneously. Mostly even the financial press doesn't highlight it because to a large company most lawsuits aren't "material" which means they don't have to be detailed in public SEC filings. They can be a big deal to an individual who, say, had their life ruined from a product defect, or lost their life savings, but they're mosquito bites relative to corporate finances.

The normal reaction from executives is irritation and propaganda against 'frivolous' lawsuits and plaintiff lawyers.

If someone is in mental distress who knows what would put them over the edge, but I don't think such a lawsuit constitutes any sort of explanation in itself.
I am currently living in a seaside town where golf carts are a normal means of transportation. You see them out and about every day. On the main highway through town, they drive on the shoulder; everywhere else, they take a lane just like cars do. The people here clearly believe they have some advantage.
I've setup mailu recently and can vouch for it's relative simplicity of setup and operation, including instructions for various of the verification types.

Hosting from home has been working for me, pending my network and homelab dramas. I haven't had trouble getting email to Microsoft or Gmail addresses

The caveat is that I don't self host my primary email address. I was going to be migrating it off Google, but they backed off enough to allow non-commercial gsuite users to remain free - and I don't want to close a door that I can't open again.
I'm interested in the community's perspective on this article.
Loading our power infrastructure with the needs of tens of millions of cars which now rely on gasoline/diesel but which, in the future, will need electric power in order to function is downright criminal in this current geo-political climate.

First, we don't even have the resources to provide electric power at decent prices as things are right now, that's why your nice 70-year lady living with her 2 cats in a house in Cornwall or something like that will see her power invoice multiply by a factor of 3 or 4 at least, thinking that bringing in even more demand for power will improve things when it comes to price is, I repeat, criminal (that old lady presumably needs power in order to heat herself during the winter, making that power exponentially more expensive won't help with that).

Second, we don't have the infrastructure. Maybe if we'll invest trillions of dollars and euros we'll be able to connect the new nuclear plants and solar farms to the main grid and transport the new extra power between big population centers, but at the "last mile" stage things are awful, for example I'm 99% sure my apartments building cannot handle one in two apartments (let's say) charging their cars at night, especially during the summer, the thing will just catch fire.
> The IKEA effect is a finding that people tend to ascribe a higher valuation towards self-assembled products compared to objectively similar products which they did not assemble.

Manager language.
"people tend to ascribe a higher valuation towards self-assembled products" which are easier to dismantle and reassemble back. I assembled IKEA furniture and other furniture. When your assembly instructions are only an exploded view of the product, you don't want to do it again.

The value of the product is given also by its utility, not only by its looks.
Anything travelling 30mph has to travel on the roads. Class 3 ebike owners who ride on shared use trails are a menace and a serious threat - to pedestrians, to other cyclists, and to any goodwill cycling has in the community.
Also consider this: https://poste.io
this has well documented and prevent going emails to spam with set DNS MX and SPF
Thanks for saying. I have some ideas in mind, like creating some courses specific to Leon. In the meantime, it is possible to support via GitHub Sponsors: http://sponsor.getleon.ai
... And a few others.

The interrelationships between corporations generally can be quite interesting, and may or may not constitute an oligopoly or cabal of some sort. This has been observed generally for boards of major US corporations, which tend to share directors, the cadre of top CEOs, keiretsu and chaebol in Japan and Korea, respectively.

Among the specific quantified measures I'm aware was a 2011 study by the Swiss Federal Institute of Technology (Zurich), which identified of 43,000 transnational corporations a locus of 147 key companies:

When the team further untangled the web of ownership, it found much of it tracked back to a “super-entity” of 147 even more tightly knit companies – all of their ownership was held by other members of the super-entity – that controlled 40 per cent of the total wealth in the network. “In effect, less than 1 per cent of the companies were able to control 40 per cent of the entire network,” says Glattfelder. Most were financial institutions. The top 20 included Barclays Bank, JPMorgan Chase & Co, and The Goldman Sachs Group.

As to concerns over this, one that the research team identified:

Concentration of power is not good or bad in itself, says the Zurich team, but the core’s tight interconnections could be. As the world learned in 2008, such networks are unstable. “If one [company] suffers distress,” says Glattfelder, “this propagates.”

<https://www.newscientist.com/article/mg21228354-500-revealed...>

The study itself is "The Network of Global Corporate Control" by Stefania Vitali, James B. Glattfelder, and Stefano Battiston. <https://arxiv.org/PS_cache/arxiv/pdf/1107/1107.5728v2.pdf> (PDF)
> The gap between tree-based models and deep learning becomes narrower as the dataset size increases (here: 10k -> 50k).

I am curious if there is a sample threshold where it's worth exploring deep learning approaches to tabular data. I wonder if there are other considerations (e.g., inference speed, explainability, etc.).
Soft skills are actually highly overrated.

The 10x developer is not a myth, it really exists.

What's better, someone who can write as much code as 10 people, or someone who can manage 10 people? Clearly the former.
It is a bit like in the Matrix. If it tastes the same and you have a good feeling when you bite into it, is there really a difference?

I mean aside from the fact that we are now entering times where the water consumption of each unit of meat produced will become a serious issue and threaten the actual survival of people.
This already exists. For a project I worked with a 'house of the future' style project. Which was build in a way that it was a faraday cage that had an option of letting selected frequencies through.
512x512 with k_lms is around 5s
In-person can make the bonding and camaraderie a lot easier for many people -- some, more than others.

That said, for the last 40+ years, people have also been building relationships online, much stronger than usual office ones. And, for much of that period, it was without even the benefit of videoconferencing. Some of my closest friends are from various open source communities, for example, and I've only ever met about half of them in-person.

I think many companies haven't yet figured out how to provide fertile soil for distributed teams to bond. And I've heard of cases where employees try to do it organically, but their style is cramped by the company (e.g., mandated corporate communications tools that aren't amenable to this, keyloggers as part of "endpoint security" having people feel under surveillance, suspicions that video calls are recorded, culture and metrics/demands that don't permit genuine casual interaction time).

Another speedbump sometimes might be for people who've grown up with their in-person charisma/presence a part of how they interact, and haven't yet fully adapted to other modalities. Nobody is tall on webcam, but a lot of other human qualities are still important, and can be expressed and perceived.
Interesting that there are multiple confirmations of all the shuttle crew still being alive. Who was on the Challenger?
The "harder" argument is the regular deliverability uncertainty, while the "easier" one is availability of some less known and supposedly user-friendly software projects. I doubt they make it easier in the long run though: as with much of other new and supposedly user-friendly software, it's tempting to recommend that to new users (and they may prefer it anyway), but then all sorts of issues arise: often it's not in system repositories, so no updates (no automated/frequently happening in practice ones, that is), and there are occasional semi-broken manual installations, then there's a lack of documentation and community, probably it'll be abandoned in a few years, and generally you get all the characteristics of experimental/immature software, where you need more advanced skills to debug and maintain it than those needed to just use mature software. Throwing that onto new users, over the much more mature software, doesn't look like a good idea to me.
I think you could get pretty far with avoiding pain and avoiding boredom.

The avoiding boredom can be seen in humans studies like https://www.science.org/doi/10.1126/science.1250830
I naturally parsed it as he has some friends who are around 30 years old. I am possibly wrong.
hi Vito! how've you been?
I think this would be awesome to develop a Tesla "skill" for. Since it's self-hosted, I don't have to worry about sharing my Tesla credentials with a 3rd party. I tried to create a quick and dirty Alexa skill to do things like check on the state of charge and lock the car, but didn't want to climb the mountain of storing "secrets" in Alexa/AWS. Keeping them local in Leon sounds much better.

I would also like to use Alexa to control my doors (garage, house, etc.) but making that available to world doesn't sit right with me. But with Leon I don't have to worry about someone hacking my Alexa account, or even sharing my credentials with a 3rd party "skill".
How in the... the Super Mario Galaxy level had enemies that respond to the camera location!

Edit: Apparently every dynamic enemy on the map has a hand coded state machine https://github.com/magcius/noclip.website/blob/19f83f77c3e77...
I agree with you, but, pitch-stuff aside, the time issue is an inescapable constraint. You can't have perfectly live simultaneous collaborative playing over the internet; things will inevitably be out-of-time for many. Due to the speed of light, you actually can never reasonably achieve this for two people maximally separated across Earth, even with hypothetical perfect technology and latency at its theoretical minimum. If the participants are both very close in physical space, like on a LAN or something close to it, latency could potentially be minimized enough to make it acceptable, but that's pretty much it.

If your goal is to make something as accessible as possible to as many global internet users as possible, you either need a) some degree of time quantization (which makes it more rigid and less musical and creative) or b) some kind of buffering and/or turn-taking system (basically, overdubbing, which makes it less "live-collaborative" / "jam-like" and potentially less enjoyable to participate in compared to something more live).

At least, this is my understanding of the problem. Someone please correct me if I'm wrong.
There are lots of publicly available databases and coding systems for healthcare / life science, but many of them are complicated for normal people (even normal developers) to use and understand.

For instance, SNOMED is an ontology. A lot of people try to use it like a taxonomy, but it is supposed to be used as an ontology. Kieth in Accounts does not know what an ontology is and doesn't want to know. He should not have to know - he just wants a lookup for medical procedure billing.

I can see the value in your attempt to present a gentler interface ontop of these more complicated and intermeshing databases. Can I recommend that you figure out how to make it play nice with Excel, PowerBI, and maybe R?
Downvotes, but no arguments? What has this site become? I might be getting something wrong here, so please explain it to me, instead of just downvoting.
On a project I worked on, we tried switching from gzip to brotli for on the fly compression, and it significantly increased CPU usage. That was years ago though so it's possible things are better now, or maybe the library we used just didn't support a compression ratio as low as what we were using with gzip.
To be fair, I'd wager that the vast majority of Americans live, work and travel within 100km of a gas station at all times. That number could be pushed even higher if you include distance from any ordinary electrical power outlet that could theoretically be used to charge an EV. It's true that parts of the Canada and the US are very sparsely populated, but EV adoption could happen (and is happening) across much of the region anyway because realistically it's still only a few people who regularly spend their lives hours away from any kind of service whatsoever.
There are multiple apps that claim to do it using the phone camera… but I’ve never tried them, so no recommendation.
True of bad managers. And in large orgs they are not isolated, usually a group under a bad director or vp of a division.

And totally agree on the work being visibly the exact same output if not more in my case.

But one example I can give is how for certain folks who want to build a professional career or want to grow, they need to know who in what group they can connect with. And in office it looks like you sometimes seeing a person many gravitate towards and ask about them and find out they are a somebody. In slack there are no similar strong signals and you have to browse many channels and who knows if they would accept your zoom invite to connect. And in most orgs, driving this kind of connection building is nearly impossible remote - asking an introvert to go be social is hard enough in person let alone ask them to browse slack channels.

And as a byproduct most people stagnate, feel alone. How do you try and make friends? How do you try to find people like you? Productivity is there but feeling of any other benefit from work is gone and lets be honest, not all software work is meaningful and clearly adds to the bottom line. Adding unit tests to a codebase is a lot more tolerable when you have people you chit chat with on your breaks or go to lunch with. Again.. big corp type work situations. But I know it is also true of non high growth startups or medium sized companies as well. The KtLo work (keep the lights on) is needed but not super invigorating.
I understand that. But it’s a bad analogy. Because when when you build something yourself it’s not the same piece of furniture.

You may love it because you made it, fine. But you also may love it because it’s exactly what you need. You may hate it because you tried to build it on a shoestring budget and you got what you paid for.
I would say based on personal observation that the more scrape-worthy an app is, the more likely it has cert pinning. Rather obvious if you think about it, really. High value targets especially from big shops tend to have other measures like complex MACs that make scraping hell.

I’m sure most largely-worthless-to-scrape apps don’t employ cert pinning.
The capitalist network that runs the world (2011)
From a conversation in another thread, this study came to mind, and I discovered HN hadn't discussed it (though there were a few submissions at the time).

The study itself is published to Arxiv: "The network of global corporate control", by
Stefania Vitali, James B. Glattfelder, and Stefano Battiston.

<https://arxiv.org/PS_cache/arxiv/pdf/1107/1107.5728v2.pdf> (PDF)
I think everyone knows this who owns a domain. Probably people say this because (like I do too) they have all the control over the name. If I rent an apartment, I do have to consult the owner to make major changes.
I'd be interested to know how the feelings change if theyve owned the piece of furniture for like a year, rather than having just felt the efforts of putting it together, etc. ie. does the value of the build effect drop off a cliff after the efforts of putting it together are no longer relevant to the builder.
From my own observations there two general reasons:

* Assembly is seen as [near] zero value add step, therefore self assembling is seen as an easy opportunity for savings, especially when assembly is actually sold service.

* People think that assembly is generally done by minimum wage employees coasting through the day and half assing tasks, therefore self assembly with a little bit of focus and dedication is seen to lead to higher than default assembly quality.