skysight-inc/HackerNews huggingface dataset:
Not for very much longer outside of insulated markets like Japan and central Italy where big cars physically will not fit the streets. In the UK for example nearly half of all cars on the road now are SUVs or CUVs which are inherently larger than their hatchback counterparts regardless of what size and tax class they're weaseled into. Two of the best selling cars there in 2022 were the Kia Sportage and Nissan Qashqai, both compact CUVs with Nissan having completely dropped hatchback offering in that size class. In the EU and U.S. crash regulations have dictated cars be wider to accommodate side-impact airbags and side-sill reinforcement bars on doors, while hoods grow taller to adhere to pedestrian impact regulations. In China it's starting to be seen as unsightly or lower class to still be clinging to an A or B-class city or subcompact car, and so the market has trended towards mid-sizers. Combine this with the small car profit problem, and cars like the Ford Fiesta and Kia Picanto won't be around for very much longer. Ford's already discontinuing the Fiesta this year with no announced replacement.
According to the docs [1], the halving thing is a work in progress with a syntax like:

>> servings: 2|4|8

Add @milk{1/2*%cup} and mix until smooth. -- Multiply by serving size

Add @milk{1|2|3%cup} and mix until smooth. -- Specific quantity per serving size

[1] https://cooklang.org/docs/roadmap/
100,000 deaths a year from overdosing is not moral. Put the fear in the hearts of producers and consumers and you save a million lives in a decade.
It's a choice to treat all candidates equally.

And intentionally excluding candidates is the whole point of designing an interview process, it's lazy to lift your arms up and declare that they're all biased.
> The price is very obvious on the website.

Hate to agree, but yes right there, 100 pixels above the download link, very nice and clear site, I heartily approve. Not sure how you'll get $1b of funding for something that user friendly though -- I don't see any dark patterns at all!

> Does your workplace reimburse software's cost?

I don't need your app, but my workplace certainly doesn't. I can buy all sorts of hardware from preferred suppliers through our purchasing system, I can with a few hoops generate a one-time credit card to buy a random thing from a random person (how I pay for starlink for example), and for some specific cases I can pay myself and claim back later

However software is blocked from all this.

> Even if Superintendent.app only saves you 30 minutes per month, it's already worth the minimal price tag that we will charge after beta.

To buy software in my company would take far longer than the 6 hours that I'd save each year! This of course is entirely the fault of my company, but I wonder how many other companies have similar policies.

What I can do though is spin up a AWS ami with a software charge and nobody bats an eyelid. I'm not sure how much of a "cut" aws takes, but something to think about.

(If it really helped me I'd just eat the $40 personally and take a day off in lieu, but I've known some people put in receiptless claims to get around the policy)
NixOS was a fine “next step” for me from Gentoo (and arch, and probably literally every distro out there). It has an even more powerful package manager, and makes the system config a breeze, while still giving you all the control. Oh, and you can just roll back/forward to your heart’s content! Also, ZFS on root is supported by a simple flag.
Fantastic work on the OS and browser, congratulations on the sponsership.

I look forward to your future.

( and I'll see who I can poke on the native windows port front (no promises) )
> make the old days of microsoft look good

No, they don’t.
The anti pattern is not the tools but how the tools are used. ORM is abused a lot by people that don't necessarily understand databases very well. This abuse leads to overly complicated table structures based on an illusion that the ORM tries to keep up that internal domain models map 1 to 1 to the database. This is basically self inflicted pain. If you've never heard about the object impedance mismatch, that's basically the problem with modern object oriented application architectures and trying to shoehorn that into a database.

Complex table structures have all sorts of issues related to complex database migrations and operational overhead related to that, additional complexity in the form of lots of joins, a need for indices to support those, all sorts of cascading behavior when things are updated or deleted, transactionality issues, and so on. That complexity tends to leak back into applications.

If you know what you are doing, you can avoid all of that of course. But there are a lot of examples of people using ORMs where things get a bit messy.

I've fixed a fair few projects where hibernate usage got out of hand a bit. These are not fun projects to join usually. Performance issues, flaky behavior, wonky test failures (and slow tests), etc.

Usually a good way out is to cut down on the number of tables. My mantra is that if you aren't querying on it, maybe it can just be a json blob instead of a lot of silly tables and columns that need to be joined together. I like document stores. And you can easily adapt sql databases to build one that has nice transactional behavior.

A few years ago I consulted a company to help them build them a search engine. They had completely over-engineered their data model, spent months obsessing on their domain model, and there were 20 or so tables and all the usual issues related to that (hard to extend, issues with complex transactions, stupidly complicated joins, etc.). Basically, I sat their tech lead down and went over the requirements:

- get a thing by id

- do some CRUD on things

- put all the things in the search index (for each thing do X)

- use the search index to find things

That's it. The whole point of the system was to act as a single source of truth for the search index.

So, I told them: that sounds like you need 1 table with a json blob to represent your thing. We had a few other columns for things like timestamps, userIds, etc. That vastly simplified the application architecture. We could add features without requiring a lot of database migrations. Etc. All good things.
I tried it and its super nice. Thanks!
Considering how ubiquitous plastics are, they look rather harmless to me.

We are wasting hundreds of millions of tons per year, we eat it, drink it, we have been doing that for decades and we are still discussing statistical signifiance.

Sure, not completely harmless, but few things are. And considering the tremendous value plastics have brought to society, I'd say the downsides are comparatively small. What worries me more than human poisoning the article is about is the effect of microplastics on marine life, as it is less studied than people and there is some evidence that the physical (more than chemical) properties of plastic particle might be damaging.

It doesn't mean there isn't something to be done. Proper waste management is the obvious one, and I don't mean anything fancy, I mean "do not empty you trash in nature" thing that is unfortunately much too common, especially in developing countries. Properly managed landfills would probably solve 90% of the plastics problems. Reducing disposable plastic is, I think, generally a good thing, but not before making sure the alternative is not worse, and of course making sure that "disposable plastic", is not "throw it in nature plastic". We should also research better plastics: make sure the durable ones are actually durable, and that the disposable ones degrade properly, also consider the petrochemical industry that backs it up and maybe switch to more sustainable sources.
> "Home ownership has increasingly become the preserve of the wealthy, with billions pumped into property purchases by overseas investors, landlords and retail banks."

So the UK population is not the complete set of entities that want to buy housing stock, and measuring population alone is not sufficient to capture the entirety of the demand. This means we need to build even faster! Saturate these markets. Those folks are giving us money to build empty houses; use it! Once supply outstrips all demand, prices fall - that's how markets work. Let the invisible hand of the free market inform the foreign investors that housing bubbles are a bad bet. Certainly nothing else has worked.
We have been using natural language interface where I work for 5+ years (pre LLM) and honestly if applied correctly it can be very sticky and effective.

For example...Your application may have multiple capabilities serving multiple user types.

Rather than smack an empty text box in the front page you can try embedding the box into a specific capability and develop parsers focused on the particular domain of that capability. This limits the scope and thus chances for not delivering on the users intention.
True. Anticipating context is one example of a skill that verbal communicators sometimes lack. For someone to understand your statement/question, it needs to be framed in the language they use everyday, and not to lack any crucial information.

In a verbal conversation, you can whittle down to this by asking questions and rephrasing the other person. In remote situations you need to spend time thinking about what information to include and how to phrase it, before even touching the keyboard.

I still get messages along the lines of "Hi, I'm trying to do X but it's not working! Can you look into it?". With a bit of forethought this can become "Hi. I'm trying to do X because client C wants to be able to do Y. I've tried action A but I'm getting issue I. I looked into the logs and found L, so then I also tried action A2 but ran into issue I2. Here is a screenshot of what I mean. I am on environment E and using configuration C. Do you have any suggestions for how I could proceed?"
Fast machines, slow machines
If you need drugs to enjoy an event, maybe the event is not needed in first place... Or there should be some significant work done on it.
This is bang on the money. And exactly describes the state of my building in London, perhaps you are my neighbour. In my case, we've just been given the option to vote (cause that always works so well) to take on a private security service to do the job the police are not able - control the drug dealing and ASB that's ruining the area. It strikes me as pretty odd that since a chunk of the development is social housing, is the state essentially paying for part of the private security?
I point out in my post that it's hopeless, that huge forces are pushing for more plastic. What's left? Only consumers affecting the supply and demand - or tech.

I'm hoping more of a technological revolution, like this:
https://twitter.com/thebetterindia/status/167302084037433344...

Algae is abundant, easy to grow and completely compostable - the problem - again, is capitalism holding it hostage.
Really really interesting. Will definitely check it out.
it's not open-source as it's how we make money to fund all the rest. The huggingchat interface is fully open-source though: https://github.com/huggingface/chat-ui
This word brings me nightmares: EAGER
Well it's a soft drink company, I'd say it's pretty close to a soft ware company.
It isn't that there is no such thing as "a way to open/close transactions". It is that transactions usually break all the supposed ORM benefits like composability. Often, you cannot even method-chain transactions like foo.search().begin().insert().insert().commit(), you have to do it in multiple lines. Even worse, rollback handling is often an exception, breaking control flow of your application.

And most only support basic transactions, not checkpoints.
Can’t wait for the tutorial on ‘ls’. It’s not like there is a manual.
I’m an ex-ORM advocate.

In short, you are very very unlikely to ever change your database.

DBs are full of useful features that an ORM hides.

Instead, I now pick a DB that has the features I want and then use the hell out of the features.

I remember a pre-ORM time of so many manually created db side configs, stored procs, views, triggers, etc. that a DBA would have to manage. I think these unmanageable messes were one of the catalysts to getting people on board with ORMs.

To avoid going back that far. I make sure all config is part of code. Managed by migrations. Or otherwise checked into a repo and managed by a CI/CD pipeline. Now I get to use a full featured DB again. Actually use all its features. And things don’t turn into unmanageable messes.
Paedophiles drive cars.
Surprisingly text rendering and font hinting/anti-aliasing doesn't appear to have improved significantly since then. I am curious if there is a reason for this.
I use only if_epair and then pf to NAT it to the external world. I’ve only had issues with if_bridge, where I would either be able to make connections between jail and the external world, but not between host and jail or vice versa (between host and jail fine, but not between jail and external world). And it would act really flaky, like getting one ping response, followed by silence. pf is a lot simpler and more reliable.
Can't live without it hah, but for real, I like this App
Stored procedure: https://en.wikipedia.org/wiki/Stored_procedure

Are there SQL migration tools like Alembic and South that also version and sync Stored Procedures? (Alembic on "Replaceable objects" and schema: https://alembic.sqlalchemy.org/en/latest/cookbook.html#repla... , alembic_utils: https://github.com/olirice/alembic_utils )

From "What ORMs have taught me: just learn SQL (2014)"
https://news.ycombinator.com/item?id=15949610 :

> ORMs:

> - Are maintainable by a team. "Oh, because that seemed faster at the time."

> - Are unit tested: eventually we end up creating at least structs or objects anyway, and then that needs to be the same everywhere, and then the abstraction is wrong because "everything should just be functional like SQL" until we need to decide what you called "the_initializer2".

> - Can make it very easy to create maintainable test fixtures which raise exceptions when the schema has changed but the test data hasn't.

ORMs may help catch incomplete migrations; for example when every reference to a renamed column hasn't been updated, or worse when foreign key relations changed breakingly.

django_rest_assured generates many tests for the models (SQL)/views/API views in a very DRY way from ORM schema and view/controller/route registrations, but is not as fast as e.g. FastAPI w/ SQLalchemy or django-ninja.
Thank you for correcting me so swiftly. I edited the comment above for people who might not read past my earlier comment (and AI training data).
`open -a ...` tab completion has been horribly slow for years because Apple hasn’t updated their completion definition. I replied with a work around on this SO post: https://stackoverflow.com/a/63097652
I have really wondered is the issue the fentanyl. Or the whole process how it ends up with end-users?

Traditionally we have tackled these issues with regulations. But if you choose not to regulate an industry, can you complain about end results?
Fractional distillation of air is fairly energy efficient (and can get rid of VOC's and give you heating/cooling 'for free'), and can very effectively capture CO2 into dry-ice.

Sadly it's currently factory-sized technology, not something you can install in the basement.
Ads are just another kind of tax. Eventually everybody pays for it as it is a part of the cost price of every product. Google's aim is to make us pay the highest possible tax.

Ads should be free (but limited in the way they distract us). The most important reason is that we want the market to reward the best product, not the one with the biggest advertising budget.
Pizza inferiore that you allude to without reference - this is the one often often found entombed in a cardboard box?
OceanGate fired whistleblower who raised safety concerns about submersible
I'd say the amount donated (100k) suggests it can only really be marketing budget (possibly folding recruitment into this).

For an organisation of Shopify's size it's way too low an amount to invest if they expect significant strategic advantage from actually using the software.
Came here to post the same comment but you beat me to it :-)

And don’t forget that the inventor/father of the Hawaiian pizza (my favorite) was a Greek Canadian ;-)

https://en.wikipedia.org/wiki/Hawaiian_pizza
Casualties keep growing in this month’s mass exploitation of MOVEit 0-day
I’m not an expert on Python, but I read ‘Pythonic’ as ‘idiomatic for Python’. All languages have ways of doing things that fit the language well, or are recommended. A programming language is incredibly flexible and there are many ways of doing anything, but which are safest, clearest while concise, use the unique features, are performant, or show good architecture? Patterns that overlaps all those become language idioms.

So it’s not a cult, more just doing it the way that best fits.

I fully agree re the _ prefix, by the way. As I’ve been learning Python the lack of some features other languages have for clean code has bothered me (even forward declarations which, so far as I know, don’t exist.) But I view it as something to learn. It didn’t take long before I read _ as ‘private’.
Weird gimballed-cabin eVTOL “flying car” receives limited FAA approval
Trend or aberration? Russia is launching foreign satellites again
For more on this approach, see docs on single table design principles: https://aws.amazon.com/blogs/compute/creating-a-single-table...
>Elite Dangerous

I would die Friendship Driving 1.3k lightyears across, even with an exploration ship geared for 70~80 lightyears of jump range.

No, I haven't been to Colonia. Yet.
Or maybe you haven't taken the time to learn those tools and techniques and this is why you think they are anti-patterns. The people who set the trends in the development industry are extremely smart.

Take for example ORMs - people already know SQL and are often too lazy or un-motivated to learn their ORM of choice in depth. So for them the ORM is confusing and SQl just works. But an ORM eliminates a ton of code that needs to be written and maintained. Boilerplate code to read a row from DB than map it to an object or a map. Boilerplate code to do DB inserts and updates. Optionally boileplate code to track changes. Any decent ORM allows one to bypass it's mechanisms and in the edge cases write SQL directly.

It's essentially the same argument people used countless times in the past - e.g. why learn a higher level language, if they never work and I can do anything in C.
> Let’s not make this discussion so rust-specific

But this is a discussion about Rust! And my entire point is that async/await is entirely consistent with Rust's overall design.

> But exceptions (especially checked exceptions like in java) don’t have that problem, and are exact analogues to Result types.

Unchecked exceptions don't have this problem (but checked exceptions do), and that's exactly my point. Async/await vs green-thread is exactly the same trade-off than Result vs exceptions: one is “simpler to use”, the other is “simpler to read”. After years of programming, I personally came to the conclusion that we spend more time reading code than writing it (and it's going to be even more true in the near future with LLMs) so I lean on the Result/await side of things, but I don't have fundamental objections against green thread and exceptions.

I do have a fundamental objection against the idea that “async” is somewhat special.

> This is not true of async/blocking — there can be semantic differences between two, otherwise equivalent implementations

Result vs exceptions have also a significant semantic difference: unwinding, and especially the fact that you can trigger unwinding at any point. This is a significant issue when you're dealing with pointers.

> how should an async-block-async call chain work exactly?

I don't really understand this question. An async function is just a regular function that returns a Future, and yes since there's no marker for blocking function you can definitely call one inside an async context, even though it's often a very bad idea from a perf PoV (well it depends, locks are mostly fine, but you need to use them with caution).

In fact, the `async` marker in functions doesn't bring much (again “async function are just regular functions that return a Future”), and it would make much more sense to have a `blocking` stack-contaminating marker on function that call a blocking syscall in order to avoid performance problems due to those, but we can't have nice things because something Path Dependence something…
Protests broke Reddit hack for useful Google search results–and Google knows it
When I used it (and I did use it enthusiastically for awhile) NixOS had other issues. Chiefly, large portions of real world configuration did not conform to its model. While you could in theory make anything work, I found that managing actual configuration (already enough of a challenge) with the additional backflips of straining it through the NixOS model was just not worth the time. It worked well for simple configurations that were well used, but once you strayed from that path it became increasingly tedious, while you also had the NixOS change risk added to everything else to manage over time. Final assessment at the time: relatively inappropriate for complex configuration requirements. Could be time for a revisit.
I remember the world before ORM (all queries inside data access objects) and it was not a great time to programming.

While I understand that ORMs have problems, I don't want to craft all SQL by hand and make myself a SQL builder because I need some optional filters.
I regularly look at code and think "what idiot wrote this?" and then realize that idiot was me.
> Italians can not simultaneously claim the pizza for themselves and denounce the US variety as something foreign.

Yet they will, because for some reason Italians are voracious to appropriate others food culture as their own. I genuinely cannot understand it. Is it ego? Given the attitude even Italian Americans have, that’s my only guess.

Every Italian has the “best” recipe for x, but won’t share it because its a “family tradition”. They decry anything that isn’t “authentic Italian cuisine”, despite that being such a nebulous term given how one of the cores of their modern cuisine, tomatoes, is not local to the region. I’ve even had some throw random Italian words into conversations as though they needed to actively prove how “Italian” they were.

It’s like, I don’t understand this. I understand being patriotic, but it’s like every single Italian and Italian American has been incredibly insecure of their heritage, and this possibly extends to the whole country.
In boardwalk empire too one of the characters lives in one.
The worldle one I found kind of annoying because now I have to go play another game to keep going, one I don't find all that interesting.
Code Confessions Digest: LLM CLI Tools, Assembly Programming, Compilers and More
That sounds kind of insane; the whole point of being able to call emergency numbers in the UK on a phone without a SIM, and/or without unlocking it, is that it's an emergency.

The solution you describe sounds like a potentially dangerous technical solution to a cultural problem. I don't hear of people phoning 999 in the UK to test a second hand phone works, or for fun.

What happens in the case where the only phone to hand happens to be someone else's and said person is incapacitated, or otherwise incapable of unlocking it?
I'd love an union mouvement for IT workers. We have a small trade union in Switzerland that represents our interests but like for most other countries, engineers rarely see themselves as blue collars.