skysight-inc/HackerNews huggingface dataset:
That's for fuel efficiency reasons. Cars lower to the ground get much better mileage at highway speeds since they have less aerodynamic drag.

And it's not just compact cars, modern SUVs, except the ones destined for workhorse off-roading, are also lower to the ground than they were 20 or so years ago since they never leave the city/highway anyway.
Tim is so pleased with the reception these videos have had! He is exactly as knowledgeable and gentlemanly as he comes across. I’ve learned a lot from him!

If you get the chance to visit his arcades in London or Suffolk I highly recommend it. The combination of humour, physical activity and engineering is wonderful.
A lot of them will magically go away, is the thing. Even more of them will magically go away if you give them actual healthcare and social workers along with the housing.
The world is not black and white.

I find those experiments until a certain threshold okay.

1 day: no problem here
20 days: still no issue.

Life doesn't start just because we let a biological machine execute something.
Only if such a community exists and is welcoming to outsiders.
xdg-utils does not use /etc/mime.types; that file is used by Apache httpd, CUPS, and various other programs though.
That's the wrong comparison. We don't need to replace generation capacity with the same capacity of batteries. Batteries don't generate any electricity after all. We need batteries to smooth out differences between demand and generation. The total amount we'll need is very much still up in the air. Better interconnects, good use of existing hydro, overbuilding renewables, shaping demand, are all other ways to balance loads and guarantee enough power at all times, all of which reduce the need for batteries.
Evergreen / Evergiven
The day before the Evergiven was stuck in the suez canal a group who refer to themselves as "the Volunteers" pointed out one of Evergreen shipping companies vessels in Boston harbor and referenced some oncoming disaster/act of terrorism. The next day the Evergiven, another vessel owned by the same shipping company became stuck in the canal on its way from Malaysia to Holland. The majority of this group lives in Minnesota. Some of them are on my computer right now, as well as cell phone, both computers have been compromised.
The heavy machinery with moving parts lifting thousands and thousands of tons is also going to need maintenance and wear&tear replacements. The problem with scale is that all these proposed gravity batteries need much, much more machinery than an equivalent pumped capacity pumped hydro or chemical battery plant.
If they checkout `origin/branchname` rather than just `branchname` then `branchname` doesn't get created locally so they don't even have to drop the old one!
I still remember Gowers doing a live problem-solve as a lecture on what he calls "splitting questions" (that is, a sub-question whose resolution would ~halve the search space for a proof). He was given an unseen IMO problem and tried to demonstrate the process of solving it this way. I would have called this astonishingly brave, to live-solve a problem that you know in advance is extremely difficult; in fact he didn't succeed. It reminds me of something one of my schoolteachers once arranged a lesson to teach, to the effect of "you'll learn fastest if you're able to guess and be publicly wrong". It's brilliant to get more examples of this.
It's not heartless to point out that most people don't care about the actual problem of being homeless except for the way it affects them, and it's relevant to point it out because it's an important part of understanding why the existing solutions have been chosen.
Buy the Dip They Said: Bitcoin (BTC) Plummets to $48000, Some (Possible) Reasons
> can't get people to take the second dose.

What is the reason? People don't bother? Are afraid? Organizational issues?
Rich people tend to hang out toghether at the same places. Some get rich by having companies, others get rich by doing illegal stuff. So you could definitely find the right connections in those circles if you want to.
I never understood why GitHub insists on creating a new commit for "Rebase and merge" when the branch is already ahead of master.
AFAIR the creator code determined which program would be used when you opened the file, as well as the file's icon.

The file type determine which applications could be used to open a file (by drag-and-drop onto the application, or via the application's Open dialog box).
> this is only relevant when you have modified the copylefted code

If I write a program that uses a GPL licensed library but never modify that library, it still infects my entire program. I have created a derivative work under copyright law. It doesn't matter that I never modified the original code that I received.

So if my proprietary SaaS web app makes use of an unmodified AGPL licensed library in order to perform a single computation ...
It's an app because we believe this way we can offer better user experience than a website. Devbook works similarly to Spotlight on macOS. You hit a global shortcut and Devbook appears as an overlay over the currently active application. We couldn't do this with a website.

We don't show any ads or resell any user information. The advertisement in our privacy policy is just a standard language for cookies when you gather basic usage data through analytics tool.

We're funded by Pioneer [0]. Currently Devbook is free. In the future, we will introduce premium plans for teams.

[0] https://pioneer.app
You're assuming that the economics that work for a mall would still work the same way when it's converted to "office space plus amenities". I know a few office buildings in Berlin that have a food court, barber shops/hairdressers, dry-cleaners etc. inside the building. And I doubt they're paying full price on the rent - they're advertised as amenities that make the office space more attractive, raising the price of the office space in the building.
On Earth, gravity has a bonus of a free massive side plate. As a battery, it might work better on Jupiter and unusable in free space, but it still stores orders of magnitude more energy than we use, in abundant cheap materials. I liked the trains-on-hills project - seems easy enough to build in large quantities and stores reasonable amounts of energy.

With electromagnetic, we are barely capable of scraping a bit of energy from the surface without the device self-destructing. Even in superconductors, only a fraction of electrons whizzes around and even high-energy plasma is a mixture of both charges.
This all provokes confusion over 2 different types of facts:

A) Knowledge of when a specific event occurred.

B) If something is true or not.

To use cases like "logged_in_at" as the example for why booleans shouldn't be used is essentially a strawman argument.

There are many situations in which a boolean fact does not occur in the time domain or have any possible value. Knowledge of certain facts in certain problem domains can be viewed as timeless even if they did come into being at a discrete point in time. For example, regulatory facts that govern entire industries. You probably never care when a specific regulation started to matter for a situation, just that it does or not. All these timestamps would do is confuse downstream users and bloat extracts of data.

The biggest problem of all is this statement:

> Storing timestamps instead of booleans, however, is one of those things I can go out on a limb and say it doesn’t really depend all that much. You might as well timestamp it. There are plenty of times in my career when I’ve stored a boolean and later wished I’d had a timestamp. There are zero times when I’ve stored a timestamp and regretted that decision.

There is nuance to this problem. A and B are both perfectly valid cases and each have their own representations that make the most sense. The discipline is in identifying these cases appropriately and using the correct tool for the job.
Having followed those proposals for a while, I can’t help but have the same question as the commenter over at the blog: at this point, why not just use C++? The features proposed are already present in C++, and the only C toolchains that I expect would implement them already include a C++ compiler as well. The effort to add those features to C as well seems like pointless busywork.
I have been using OpenBoard [1] to teach my classes, but this seems better.

What I am particularly excited about is Stylusboard [2], which apparently lets multiple people collaborate in real time online. This is going to make research meetings much better.

[1] https://twitter.com/wtgowers/status/1385364812239183872

[2] https://github.com/styluslabs/stylusboard
Majority of these operations are being run from Asia, so it does complicate a lot of things.
> ... who will eventually make it some day

I believe there is a term for this, "temporarily embarrassed millionaires"
foo_t foo = {.bar=1} ; doesn't work in C++.
That's why you should use trains, which can safely go a few km high in good terrain.
We are at the beginning of ev and you already can buy them at affordable prices just not yet in every category.

Give it time. Right now a ton of money gets invested into batteries and co.

When you look how much impact proper market penetration is for prices (see smartphones, solar energy etc.) It will come and fast.
Is this Qanon bullshit?
The system bring talked about here can deliver 250kW during 11 seconds max.

That is LESS than 1 kWh of energy storage.

I hope it's not the one on the picture otherwise their cost estimates are way off and two orders of magnitude larger than current lithium batteries, even taking into account battery replacement.

Another problem would be the ever-lowering price of batteries comparing unfavorably against this good old tech with stable or raising costs (human costs tend to rise over time)
Yeah almost nobody drives those here. They would take every single time 2 parking spaces and stick out big time, and as mentioned in this thread its mostly a vanity car. Most of the underground parking wouldn't be accessible with it. Contractors/small companies have vans which are much more useful for actual work (ie load capacity, permanently covered) and cost less to buy and run. Which are the most important criteria to run a business successfully.

For personal driving, either fugly SUVs or wagon types offer much better... well everything. Operating costs, much better driving experience, you can actually park it everywhere.
Frontend Components with Golang
Homelessness exists in cities because it's possible to be homeless in cities. It's not possible to be homeless (without a vehicle) outside cities. Ergo, cities cultivate homelessness. If you make living as a homeless person impossible in cities, homelessness would disappear.
As the storage cost is very low, why not use both? Not trying to be obtuse, but I genuinely typically have separate columns in my schema design for booleans and the timestamps of these events flipping from false to true (published, edited). Come to think of it: These events warrant saving them to a separate table altogether; booleans represent a current state - there may be 1:n events like multiple edits.
From the Wikipedia article you reference:

> Criticism

> Several sources point out that the banana equivalent dose is a flawed concept because consuming a banana does not increase one's exposure to radioactive potassium.[11][12][1]

T> he committed dose in the human body due to bananas is not cumulative because the amount of potassium (and therefore of 40K) in the human body is fairly constant due to homeostasis,[13][14] so that any excess absorbed from food is quickly compensated by the elimination of an equal amount.
Care to explain the downvote?

From Oleg Kiselyov's 2012 paper Iteratees [1]:

Lazy IO is so irresistible that it was added to Haskell
despite the reservations of its inventors and the failure
to develop good techniques for reasoning about its correctness
[7, Sec 10.5]. However benign, reading is an observable
side-effect, whose occurrence may have to be correlated with
other side effects. Such correlations are crucial when
performing IO over communication pipes, which is typical of
web servers.3 As Launchbury and Peyton Jones feared, Lazy IO
indeed "gives rise to a very subtle class of programming errors".
We have seen deadlocks; mishandling of IO errors; running out of
file descriptors and similar scarce resources; unpredictable,
volatile and sometimes unbearably excessive use of memory. We
illustrate the splendors and miseries of Lazy IO in §2.

This is a very famous Haskell programer's opinion on the default IO in Haskell, and he quotes that one of the main creators of the language himself anticipated such problems [2]. Why downvote a comment in 2021 challenging the claim that "Haskell's had a great story around IO for 29 years"?

[1]: http://okmij.org/ftp/Haskell/Iteratee/describe.pdf

[2]: https://www.microsoft.com/en-us/research/wp-content/uploads/...
Its reasonable to imagine that a planet founded by scientists and engineers, and populated only by scientists and engineers, will not have the problems found on Earth.

You would probably have a society composed solely of people with 120+ IQs, for example, which would present an amazing gene pool for further population expansion.
Great photos, and a great website too.
Facebook to Ask Users About the Negative Experiences Faced in News Feed
Facebook is trying very hard to fix out the News Feed, it is asking the users about the type of content they want to see in the News Feed. Approximately by next month, the company is going to start with the survey and will ask the users about the type of content they are experiencing in their News Feed. Facebook will also survey, whether the content in News Feed is too much political content or not.
It's hard to believe that it's been over 50 years since humans have been outside of low earth orbit. It's like we sprinted forward so fast, going from horse drawn carriage to space flight in a generation, only to get frightened and recede back from the highest point, never to go back.

Granted there has been an enormous amount of innovation in the last 50 years, but by some accounts we've been going backwards. Humans are no longer capable of mach 3 flight, or making Roman concrete.

I think we assume that technology will keep progressing. We assume Moore's law will continue into the future and we forget that there are people behind the progress. The technology that produced those pictures are gone, we might be able to take ones like them again, but never with the same rockets and never with the same photo-chemical processes. Progress is fragile, not inevitable and everything we have can be lost in a generation just as easily as it was made.
Maybe you're thinking of "event sourcing"?
second hand has way smaller footprint. Also your take about signaling wealth is hilarious. Do you think reasonally educated women would prefer a guy with luxurious clothes? For me and my network that would be obnoxious.

There is also counter signalling which you can read about. It explains why billionaires in Sillicon Valley wear H&M t-shirts and not L&V
A model turns into a gamble if you throw your hands up and claim that its impossible to have a 100% authentic model of a domain.

If you truly believe this to be the case, then you have not tread far enough into the forest of SQL, 3NF, BCNF, and the relational calculus. It is possible to use math to prove that a problem domain is modeled appropriately. With SQL and views, you can construct extremely high-order representations of domains that would otherwise be viewed as pure magic by any outside onlookers. The only way any of this becomes possible is if you have solid foundations and the courage to produce exceptionally clean models.

Yes, you will definitely screw it up a few times. We started over 4-5 times. Plan to iterate. Start with your domain modeling. You can do this shit in excel. No one gets too salty when you have to throw away a spreadsheet.
I did a bit of scratch math with the notion this might be more suited for individual, home power storage rather than grid supply - You need something in the order of a 5m tall tower bearing 73 tonnes to store 1 kilowatt hour (even then, ignoring conversion losses). So that's the weight of ~ten class-4 fully laden heavy trucks.

Once you can get it up in the air then the higher you can go you're doubling your storage in a linear fashion. Hoist one of those trucks to 50 meters (perhaps you have a handy cliff in your backyard) and you've stored as much as the ten trucks did at 5 meters.

So yeah scale seems hard, but the low technology/materials requirements and potential for gradual scale-up make this worthy of deep investigation. I think there's a lot of wandering off into dead-ends as far as limitations go though - Solutions that depend on a lot of concrete pouring, for example, are a no-go if the end goal is reducing atmospheric carbon.
Dutch MPs had a call with deep fake imitation of Navalny's Chief of Staff
It would also select for health conscious people with at least a little disposal income
Batteries do not replace power generation capacity directly.

They can, however, be configured to cover huge surge loads for short moments, or smooth out small discrepancies over a longer span, in more or less the same footprint.

If you want a GW of coal, you need a GW plant, whereas with batteries you can decide between a gigawatt-hour or a 1000 megawatt-hour using a similiar footprint (scale to capacity of chosen technology).

This reduces the need for significant unclean backup capacity, and either decommissioning them or reducing their usage.
The Derp Derp does get old.

FWIW though checkout Symfony as well, a lot of what Laravel gets right Symfony got right first and a lot of what (imo) Laravel gets wrong Symfony also gets right.

Plus: It never hurts to see how the other side does things because it gives you the chance to steal bits that you might need later ;).
Too bad they don't seem to provide the actual report anywhere (and neither does ICL), they just quote a single chart from that without any details. This feels fishy to me - I'd want to look into the cost basis they used, as a key problem with comparisons against batteries is that the battery cost has changed so much over the recent years (halving every 5 years or so), and many studies quote their battery price calculations on older reports that are now off by a large multiple.

$367 of LI batteries at year X is $171 of LI batteries at year X+5 and $86 at year X+10, so it's important to look at what the X is in their study. And of course, we should consider that chemical battery costs are expected to decrease in the near future, while the cost well-established mechanical components would stay stable.
I guess a compromise could be the following: upon receiving an organ donation, the recipient is asked to consider donating their own organs once again.
Great game back in the day!
Its not really linux but elf loader + shim that implements enough of linux kernel to run wine
Can NFTs be used to fund charities?
Do you think this is technically feasible ? Desirable ?
That is all true. You can however increase the effective alphabet size by working with n-grams of the needle rather than bytes. Even a 2 byte n-gram gives you an alphabet of 65536. You wouldn't get all of that as the hash table would probably be smaller, but you can increase the shifts a lot for longer patterns in this manner.
Here's an idea: what if -- instead of digging a deep hole into the ground -- we use the tower of a wind turbine as the vertical space in which the weight is raised/lowered?

A wind turbine is already equipped with a generator, so it'd be a matter of building some sort of "switch" which would make it either: (a) generate electricity using the turbine, as per usual; (b) raise the weight using the turbine, thus not producing electricity; (c) generate electricity by connecting the weight to the rotor/generator, while lowering the weight.
It's worse than that - the auto companies reduced their orders because they predicted covid meant that their sales volume would drop - turns out they were wrong, and now they are bitching and moaning because they can't get the stuff they didn't order
For those looking for more amusing assembly syntaxes, I present Blackfin, which looks almost HLL-like at first glance: https://github.com/torvalds/linux/blob/b8c9c8f0190f4004d3d43.... In terms of expressiveness it’s about the same as any other CPU-level assembly, but the syntax is pretty wild.
Woah, I used this tool all the time while debugging hoppy.network! Do you still work at Cloudflare?
GDPR only applies to personal data though? Like you can't store gender info "in case it's usefull later". I really don't see how a timestamp can be used in that way.
Yes. Maybe there are some fair points there. But mostly mr. Chang comes across as nationalistic and arrogant. The US obviously can do chip production and also at scale. And maybe this is a hint that TSMC is not being quite honest in their pursuit of an American production facility and this may end up a bit like the Foxconn story.
Long Boolean! Yes, no, don’t know, weekdays only.
It sounds like they are sharing memory and the shared memory is getting accounted to whatever tab was opened first until it closes.
Running arbitrary code from users in CI is one thing. Automatically merging code is another, which is what this bug exploited.

The former can be made somewhat/reasonably safe. The latter probably can't.
You really need to take the power and "reality distortion effect" of propaganda during the Cold War into account.

Massive projects were started without much rational sense just to beat the other side in an imaginary race (and a very concrete military race). What's the point of landing a man on the moon, if the technology to do so was so rushed and held together by duct tape that it wasn't useful for anything else? What's the point of the Space Shuttle if launches were more expensive than disposable rockets? What's the point of the Buran, if the Soviets didn't feel like they need an answer to the space shuttle "just in case", even though they couldn't see any point in the shuttle design (except as a nuke carrier)?

Etc... etc... the list goes on for both sides. I rather have slow and steady progress that actually makes economical and scientific sense in the long run.

PS: I thought the secret of Roman concrete had been cracked long ago (a certain type of volcanic ash)? But it's just not economical to produce large quantities since modern sky scrapers are not expected to "survive" for thousands of years anyway (and AFAIK the Romans didn't know much about the special properties of their concrete either, it more or less was a "happy little accident").
Forcing suppliers to hold 3-6 months inventory is also a clever trick to make one look "lean".
You can implement an append-only database, where each record is a snapshot of the latest version and a timestamp of when it was updated.
I'm not sure anything is perfect but in practice I get zero problems on the iPhone and used to have quite a few with antivirus on a Windows pc.
I'm not sure yaml and ruby have anything to do with it. This is a common risk with all centralized package management systems. It's ultimately a tradeoff of trusting a third party for the speed and simplicity. The alternative is building everything from source, or hashing your own binaries. If anything, this is on Apple for the inexplicable fact that they haven't implemented native package management in macOS yet.
Also, from the point of query optimisation this is a really bad idea. Usually you DO actually care about size of fields in SQL databases, because something like BOOLEAN is usually stored as single byte (or bit in a bitfield) vs 4 bytes or even 8 in case of timestamp. This not only multiplies on disk usage by at least 4 times, but also makes ALL indexes using this field way bigger. Also boolean indexes can be compressed (or stored as bitmaps), while timestamp indexes contain lots of unique values, so they can't be.
This is also the reason why serial IDs are way better than UUIDs for internal IDs.