skysight-inc/HackerNews huggingface dataset:
Pizza is one of those things I can't believe someone "invented". Flat bread must have been the first kind of bread: you just mix flour and water and heat it. Put something on that flat bread and eat it together and you have a "pizza" as much as this fresco is a "pizza".
> I just wanted to mention airthings. Turn key, cloud enabled, and "just works".

Cloud. As soon as it's in the cloud, it's not yours.

Just a matter of time for the next round of closing some API and boom there goes your access to data.
> His main idea, exposed in The Entropy Law and the Economic Process (1971), was that economic organisation is a continuation of biological organisation. Why? Because all machines are necessarily made of materials and use energy, and because all labour involves our biological bodies, which are also made of materials and use energy. The economy is – unavoidably – a bioeconomy, which means it is a subsystem of the larger finite and nongrowing ecosystem that is the Earth.

The problem with Georgescu-Roegen's bioeconomy framework is that biological systems are highly constrained in the degrees of freedom they can change in the short run versus the long run. Whereas the global economy as conventionally understood can change much faster after a relatively brief period of time. It's the type of metaphor that obscures more than it reveals I think.
Parent is using that data to make their point (maybe even likely directed from the tweet you linked)
recipemd is an alternarive that can do this.

https://recipemd.org/specification.html
https://recipemd.org/cli.html
I want to know it's there any way to manage logs produced by a OpenRC service like `journalctl` in systemd?
Re: your first paragraph, my hunch is that:

1. renters are less invested in the local politics given their more flexible and transient nature, therefore they care and vote less than people who have assets and multi-decade skin in the game
2. voters aged 45+ are less likely to be renters, given lowered likelihood of moving with age, and the higher likelihood of having locked in cheap real estate decades earlier. Those voters also tend to vote more
3. therefore renters are far less represented in elections

Entirely possible the above is wrong, there might be data showing otherwise.
There is an old joke somewhere about some monk and a programmer who is looking for enlightenment and circling through OOP, realizing it has always been FP, which has always been actors, which has always been OOP..
That’s why you buy NICs with hardware timestamp support and enable PTP. You can detect clock drift within a few packets.

Race conditions are mitigated, not by clocks, but by other logics. The clock was just something done after frustrations in reading distributed logs and seeing them out of order. Logs are basically never out of order any more and there is sanity.
I’d love to see an unhinged person message his sister/wife/mother thousands of times with threatening messages and see how he would respond.
An app that teaches coding, without a computer
Who needs drugs, when AI develop cancer treatment in just 30 days (according to https://nypost.com/2023/03/20/ai-develops-cancer-treatment-i...).
I think this is one of those "race to the bottom" things where businesses endlessly undercut each other until everyone loses
Yeah, how many houses are there?
I also see this happening on `mspaint`.

For example, when you 'accidentally' click the help question mark instead of the exit cross, it will open Microsoft Edge with a search on Bing for "help with paint in windows".
It's a shame you don't get to see what the other person voted for, whether they thought you were a bot or a human.
>Perhaps there’s a case for Uber… having a decent app-based way to summon a ride is a net positive. But the experience is even better in European cities where Uber has successfully integrated with the local taxi system rather than competing with it.

You'll get very different answers about Uber depending on who you ask, and in what country they live.

I think all this really points to the regulation of taxis being a complete and utter failure in much of the US, especially certain large cities there.
> Shouldn't the workers in the rich countries be terrified of remote work? You essentially open up against competition from much cheaper places and you might end up moving there to be able to match the margins.

Offshoring hasn’t been an amazing success story so far, what you save in cost you spend in fixing low quality, bridging cultural gaps, and herding workers with no skin in the game who can’t afford to gaf because they’re paid so little in comparison.

Companies will always offshore but I think it’s the jobs at the crappier companies that are offshored and these aren’t the places we typically want to work at anyway.

I’m talking about large body shops whose value proposition is “we’re cheaper and we work harder”, not about individuals around the world who are hired by 100% remote companies. The latter are typically pretty good.
Yeah, sqlite has been my preferred method for working with csv files for a long time. I will say that one nice thing about DuckDB over SQLite is that it does a better job inferring column types than SQLite does.
Disagree. All too often, JPA/Hibernate dumbs the relational model down into record-at-a-time processing with navigational queries reminiscent of pre-relational network databases and counting and joins implemented by unnecessary fetching and client-side processing rather than aggregate queries and joins. Furthermore, it brings fuzzy locking semantics/locking as a side effect of lazy/eager fetching and artifacts such as a pattern of unnecessary "id" columns due to lack of support or asymmetrical and idiosyncratic handling of compound keys, also extra magic for "many-to-many connectives" (the wording alone is non-relational), lack of attention for decimal arithmetic/overflow with money values, idiosyncratic date/time conversions and mappings of enums into ordinals, etc. etc.
The article leaves out a few weaknesses of ORMs

1. inability to represent arbitrary query results. Results get mapped back into 'domain-objects'. Now you've removed yourself from the extreme expressiveness of the SELECT statement as well as GROUP BY, pivot tables etc. etc.
The best you can hope for is domain objects that are only partially initialized with values.

2. lazy loading of attributes - certainly configurable, but if you rely on SELECT statements being generated while you are navigating a 'persistent' object, you will run into unexpected performance issues.
To solve those, you then start to eagerly load domain data for certain access patterns. More annotations, more configurations and more ... stuff - where a nice SELECT query would have sufficed to get the data you need.

3. Troubleshooting is a pain. Especially if you rely on dynamically building queries. Have fun getting the actual SQL that was run and then translate back and forth between SQL and the query builder syntax to optimize it - if you can even optimize it.

4. Doesn't treat data as data. First of all data coming from SQL queries is stale the moment it arrives in your objects. Trying to pretend otherwise and having an object graph that pretends to be the living counterpart of the state in your DB is foolishness.

5. No/limited control over writes/updates.
The moment you rely on your ORM to create UPDATEs and INSERTS to reflect the state of your object graph back into the DB, good luck with your chosen locking strategy and good luck optimizing those. Pessimistic locking is the best worst you can hope for.

Stay away from ORMs (as in Hibernate and its ilk) and treat data as data. Use structs/records.
There's a ton of survivorship bias here too. Older houses that we're familiar with were well built, which is why there's still here. Plenty of poorly built ones are no longer around.
At some point there is an objective underlying reality. I've worked at a lot of places and never seen SQL done well; even the people who were happy with SQL had no automated testing, no compositionality to speak of, and a crappy deployment model (and would usually acknowledge all this! They just somehow didn't mind). If one person uses a tool badly that's maybe a problem for that person, but if everyone uses the tool badly that's a problem with the tool.
It’s a project for fun (a hobby), and given away for free. 10 minutes of downtime every 20-30 years is perfectly acceptable to me.
Both of these things are only a matter of knowing the tool.
Also added a message that this happens for mspaint on Windows: https://news.ycombinator.com/item?id=36502731
> if SAE becomes the organizing body for the maintenance and upkeep of the standard. Is this SAE's role?

Yes, just as IEC maintains the standard for Type 2 and CCS Type 2 Combo plugs and inlets. The latest revision of IEC 62196 specifies support for up to 1,500 volts and 800 amps for DC charging:

https://en.wikipedia.org/wiki/IEC_62196

It'll be a while before cars and chargers implement that.

> For example, program Superchargers so only Tesla cars will receive higher charging power but downrated for other EVs?

Some EVs are already downrated in practice because Tesla chargers are only 400 volts which means 800 volt EVs can't achieve their maximum charge rate.

The maximum the Kia EV6 can charge at on a 400 volt charger is 100 kW, rather than the 230+ kW it can achieve on an 800 volt charger. On a Tesla V4 charger an EV6 can only get 42 kW at the moment:

https://www.youtube.com/watch?v=sEJ2KtzMeh8

On a Tesla V2 charger it gets 97 kW as expected.

All chargers in North America will be CCS chargers just with Tesla's plug on the end. If Tesla chargers still can't deliver 800 volts then the solution is to use another one that does.
After reading through the Carmack all-staff memo linked at the bottom - man I wish I’d been in a position to work for / be mentored by that man.
It's unclear whether the demand would support a higher price I guess.

Alternatively, another way of looking at this is perhaps that the distributors are seeking a profit, and so are demanding low prices from the manufacturer, meaning that high cost manufacturers go out of business, reducing supply. However, this may be inefficient, in that demand may exist at higher prices, that could support more manufacturers if not for the distributor.
Oh, and one other that I have used:
https://www.brultech.com/greeneye/

I had one of these in my old house. A little older tech, and I had my own code on a raspberry pi getting to data and putting it into influx. The IotaWatts are much more plug and play, but still it is an option for the DIY.
The matter is way past superficial personal accusations. And the people at these Twitter links have no technical background in chip design (why would anyone listen to them?). Sergio's and Zoubin's tweets are obviously and verifyably wrong.

Nature confirmed to reporters that they are investigating the paper.
https://www.theregister.com/2023/03/27/google_ai_chip_paper_...
> How many man-hours have been wasted on ORM, XML, annotations, debugging generated SQL, and so on? It makes me cry.

Agreed. All my greatest successes with ORMs have been ripping them out of projects I've inherited. The results have been more maintainable code that's faster and less resource intensive.
The series of tweets don't seem coherent and the data therein questionable at best, but if it happens, I'm sure there won't be too many people shedding a tear for the people who've made it their job to inflate housing prices everywhere
Why doesn’t it make dimensional sense to average across tenants?
You don't have to, but you have to admit DuckDB is quite nice for handling csvs quite a bit more intuitively than awk
> I miss graphite / whisper.

as someone who had to manage a system like this, i certainly don't. it doesn't scale well, it requires way too much upfront design thought (since metrics are stored in arbitrary dirs), and it's a massive pain to install and manage. not to mention, it's barely developed anymore so much needed features (like carbon cache restarts not taking a million years bc of the slow sequential flush to disk) will probably never see the light of day.

for better or worse, the industry moved on. speaking personally, prometheus is so much better than graphite ever was, in every conceivable way.
You could buy a Bosch BME680 or similar for $20 and add it to a Pi or Arduino.

A commercial model is around $200.

There are a lot of options so decide if you want to build it or buy it and plug it in!

Then you can list your data on a site like https://explore.openaq.org/
Yes thanks- probably an issue with my $PATH
They do have a well defined order, just not one based on time.
For now the data may show difficulties, but at some point, people need a job, and if only onsite is offered, will 'talents' keep being picky? Not so sure someone laid off once or twice in 2023 will be. Remote as we've known it during the pandemic is not going to stay, and all those that have made a move to a city for a better (personal) life will be stuck in the mid term, if they are not lucky on their next job search what will they do? I know this isn't popular opinion, but if some level of hybrid will probably remain on the long run (e.g., WFH once/twice a week doesn't hurt productivity and provide a great improvement for QoL) I don't see remote being the new way of working we have enjoyed in 2020-22. This is gone.

edit: typo
Interesting. I've been learning/using rust for work for the last 3 months.

I'm at the point now where I'm productive (took me over a month to even get to that point), but I still feel incredibly slow compared to Typescript. The compilation time doesn't help.

Anyway, thanks for the perspective.

I'm still skeptical that the survey reflects honest feedback given Google's culture, but perhaps I'm just biased from how long it's been taking myself and the rest of the team to achieve a higher level of productivity
You're right, I meant water+flour+starter denominator. Didn't figure salt would matter enough.

My math brain wants everything as a percentage of a whole, but I see how it's simpler the way it is. Especially since the starter also has some relatively unknown amount of water and flour inside itself.
It’s a blockchain PaaS i think
There is an argument about the open source models causing more innovation and thus more industry and/or competetive advantage of a nation. So I can't imagine that control is the only thing they are thinking about, though surely they are thinking about control.
Your idea makes sense but that recipe of yours doesn’t sound like any pizza I want.
Jesus H., the churching going demographic will love grocery-getting at WalMart in this monstrosity that screams compensation with green flavoring. It's too damn big and heavy, wasting energy and creating a risk to occupants and bystanders with truck design skipping car safety standards. I'd prefer buying a Datsun tiny truck with a blown engine and throwing some EV kit and a zillion battery packs in it for <$50k.
> > Another selling point which is "you don't need to know SQL"

> It has never ever been a selling point by anyone with an ounce of brain.

Every project I've been involved with that got saddled with an ORM was originally justified "so junior developers don't need to know SQL".

Which is a great way to paint yourself into a very painful corner, but that's what teams do.
The logical next step is creating virtual machine and brute force generate function with less then 27 instructions and see if it produces something close to sine. Let it run for few months and surely it will find something.
> On the whole, I don't see how if the authors were academics with Tenure, they'd survive this one. This is entirely NOT how it's meant to work.

WDYM?
>Lead pipe but instead of a dozen people in the pipe factory it's a few hundred

You haven't been in a factory lately, or toured one from 100 years ago?

Its exactly opposite to how you say. Mechanization slimmed the employee count, then automation did it again, then again with everything going digital.

This is seen in all sorts of industries.

The plant I work in has loads of empty offices, former machine shops bereft of millwrights/used for storage), and only half the lockers in the change room are claimed, and that's after they carved out a locker room for female employees. And that's only a 50 year old place.

One night I was working alone, and the site labour supervisor was the only person I saw all night, as he stopped in a few times to check on how I was doing. I asked him how many people he had on site, and he said about 30, including he and I. Since then, when I work nights, I check up on people too. Its a big place. The population swells during the day, but most of it is contractors(like me) and office personnel. But the plant runs 24/7, as much as possible.

I've worked nights in another part of the plant, in finishing/warehouse/loading, and there's about seven people there overnight (and the same during the day), and only one (me) doing actual physical labour(and not hard stuff at all). Because product is mechanically wrapped, packaging is machine counted and printed these days, not hand lettered, moved around via conveyor and forklift, and loaded for shipping with machinery. Even closing the rail car doors is done with a machine.

Even 50-100 years ago, the world ran much more on muscle power and human eyes, and many more employees were needed.
I'm not fully clear what you mean by don't delete lock file when the problem is the open source developer decides to unpublish their npm package
My understanding is that the CSV is read in chunks, and then each chunk is parsed in a different thread.

This is the description in the experimental PR (parallel CSV has since merged into the main branch)

https://github.com/duckdb/duckdb/pull/5194
Is it possible you and your parent (my child) are deepening the sarcasm to indistinguishable degrees? I think not, but I like to imagine.
Changing the database for an existing system happens very rarely, but changing the ORM or language is even rarer. So learning the ORM well is just as rewarding as learning the database well, IME - and more so once you take into account changing jobs, since you're more likely to take another job using the same ORM but a different database than vice versa.
I kept skimming to find the "real" article. Couldn't figure out if the schtick ever ended but I found it too distracting.

I say this as someone who spent 10 years dreaming of working for The Onion.

I feel this type of tone can work as a brief intro/aside, but is rarely suited for long form. I certainly don't think it befits a technical topic.
You can buy a $200,000+ hybrid Mercedes-Maybach S 580 that gets 16mpg city, 24 highway...and both state and federal governments will give you a nice big fat check for many, many thousands of dollars. It could be the fifth car you own, which sits in the garage of one of your summer homes in the Hamptons, for 10 out of 12 months.

Wringing out hands over people not using a subsidized e-bike "enough" seems pretty silly when for two decades we've been handing many thousands of dollars to anyone who has a pulse and buys a hybrid or electric, with little or no conditions. No income/worth caps, no purchase price caps, no annual usage requirements, nothing.
This seems primitive. I see there is some understanding that there needs to be "cookware" elements, but how am I supposed to indicate it requires a brick pizza oven or a tandori oven? These aren't trivial cookware. I'd want some way to filter these out without having to go through and indicate the 500 large appliances I don't have before I can see which recipes are feasible.

I could add metadata tags that would indicate just what the dish was (entree, or a fancy breakfast/brunch, or a desert, etc), but since there's nothing like a standard tag if anyone else gets the file those tags are mostly worthless (their software won't be able to sort a bunch of recipes into the correct categories).

There's no way to indicate how many times the recipe has been verified (apparently the vast majority of online recipes are made-up bullshit that even the author hasn't bothered to cook even once).

Even pictures... I might want more than one non-step picture for the recipe.

Naming convention is whacked out. This works for 5 recipe files in a folder. What happens when I have 80,000? Or 2.1 million? r/datahoarder would be disappointed. How many different pot roast recipes is that? Is it only eight dozen, or is it more like 900? Are they all just numbered, 1 through n?

Hell, there are some classic recipes that are seasonal. They want not just "chicken eggs" but "spring chicken eggs" as opposed to summer or fall. How do I filter those out so I don't see them in November?
5x simply not true
The editorial "A Critical Analysis of the Evidence for the SARS-CoV-2
Origin Hypotheses" in the Journal of Virology at https://journals.asm.org/doi/pdf/10.1128/jvi.00365-23 compares the different hypotheses:

> Here, we summarize the scientific evidence that informs this debate to provide our fellow scientists and the public with the tools to join the discussion in a constructive and informed manner. Our goal is to dissect the evidence to make it more accessible to those interested in this important problem. ...

> Based on the scientific data collected in the last 3 years by virologists worldwide, hypotheses 1 and 2 are unlikely. Hypotheses 3 and 4 cannot be ruled out by existing evidence. Since hypotheses 1 and 2 support the lab leak theory and hypotheses 3 and 4 are consistent with a zoonotic origin, the lab leak- and zoonotic-origin explanations are not equally probable, and the available evidence favors the latter. ...

> The best existing scientific evidence supports a direct zoonotic origin. As new evidence continues to emerge from scientific studies or other investigations, our understanding of the origin of SARS-CoV-2 will continue to evolve. Nevertheless, it is possible that its origin may never be known with certainty. ...

> Given the currently available evidence, the two plausible possibilities for the origin of SARS-CoV-2 are not equally likely. Continuing to frame them as such does us all a disservice, dilutes our efforts, and misdirects resources—only serving to weaken our ability to respond to future pandemics.
> reduced API access, worse free plan, and increasing costs.

Expect a lot more of this over the next year. We've all gotten used to generous free plans due to the era of zero percent interest and high growth; that era is ending (at least temporarily). Almost every SaaS business that has not already re-done their pricing tiers since the interest rate hikes is in the process of doing so. Oh, and ad-supported plans are going to get way more aggressive on the ads.
The xml spec needs to be complemented with xsd, relax-ng or whatever schema tool is popular these days, yaml includes that.

Still in the same ballpark I expect.
Beer factory leak turns the sea red in Japanese resort city
> Proxomitron

Oh man, that's quite a nostalgia-trip right there. Setting up custom rules/transformation was probably one of the main things that steered me into a software-development career, along with client-side scripts for Starseige:Tribes. Apart from advertisement/privacy stuff, I remember using it to customize and streamline the appearance of web-forums I often visited. (e.g. TribalWar and AntiOnline.)
https://www.aftfasteners.com/grades-of-bolts-bolt-grade-mark...

Think of all the things this chart promises. Then assume none of them.
Even if gas leaf blowers weren't terrible as far as emissions they are a weekly menance for apartment dwellers so I am hoping they will be banned where I live eventually. Electric is somewhat annoying but tolerable.

A complex pays for regular landscaping services which turns into hours of painfully disruptive noise pollution often in the early hours for residents.
Yeah and programs should also be simple, but there would be no value to them that way.