skysight-inc/HackerNews huggingface dataset:
Well, agree that name calling is not acceptable. But you know, another thing that doesn't fly is mischaracterizing someone's comments. If you mean my "ill informed or dishonest" remark qualifies, then I will dispute that. But I believe "wild fear mongering" fits the bill, but that wasn't my comment however.
create view max_products_sold as select sale_person_id, max(no_products_sold) AS no_products_sold from sales_department_details group by sale_person_id;

select sale_person_id, sale_person_name, no_products_sold, commission_percentage, sales_department from sales_department_details natural join max_products_sold;
Sorry, seems like we are speaking past each other. Considering that everything you have just said may very well be true, I believe what the original question meant to ask is "how is the [modern-day] US a preferable super power to [the other modern-day options]". I do not think the original question was engaging in a thought experiment of "almost true" realities or alternate histories.
At the heart of Bells inequality in physics is the assumption of free will, that the experimentalist is "free" to choose a detector setting.

Yet when faced with the task of actually generating random numbers, humans fail miserably. Some how the failure to generate random numbers isn't seen as a lack of free will by anyone.

But in the context of quantum physics, the experimenters "freedom" to do something most humans can't actually do is a given, and denying it is "super determinism" and anti science.

It's funny that physicist take the freedom of their random choices as a given when a simple experiment shows they don't have such freedom.
If you ever use @apply,you need to come up with a name. I prefer a few @aplly classes to meaningless clutter of tailwind detailed styles.

You could of course have a policy to never refractor - but then you might need to enforce alphabetical use of tw classes to more easily keep styles in sync accross your codebase?
Does it work with US accounts? It seems that no option for registrar to my US account.
> every project seems to end up using their own definition of breaking change

This is natural. People naturally have different notions of what a breaking change is. For example, in C++ land, an incompatible change to an ABI is a breaking change, whereas in Rust land there's only a handful of types with stable ABIs. What "breaking" means will differ by language and ecosystem, and the goal is to find a useful definition for your particular context. Semver acknowledges this, which is why it deliberately refuses to strictly define what constitutes a breaking change.

Let's also keep in mind that every language makes tiny breaking changes whenever they think they can get away with it, including legendarily-stable enterprise languages like Java and PHP (look up the "compatibility guides" that accompany language releases). And that's not a bad thing; engineering is a science of tradeoffs.
Typora is fully offline and works on real files, there's no cloud dependency here AFAIK. At most you can keep files in your Google Drive/OneDrive/Dropbox syncing folder to make it "cloud".
Thanks to nuclear Ukraine was (is?) selling electricity to the EU even during this war. Their nuclear power-stations has shown surprising resilience.

Long term is exactly where nuclear rules.
The Motivation Factor - its about hmthe connection between intense physical exercise and a whole host of mental benefits. It showcases a high school from the 1960s that had an insane PE program, and the benefits for their schooling as well as setting a positive tone for the rest of their life. Pairs well with the book Spark: The Revolutionary New Science of Exercise and the Brain by John Ratey
or, the fine article :)
I remember that day very vividly, I was going to court against my father that day. Waiting to get called into the court room for the start of the day when suddenly a bunch of police pop up and say "Everyone must evacuate the building immediately, court is dismissed for the day."

Get in the car, turn on the radio, and right about then news of the second plane dropped. I knew that was going to be a change across the country right then and there.

Never actually got back to that court case. I think literally every case got an emergency dismissal outright due to that event, as neither myself nor my father ever walked back into the courtroom after that event.
From why I understand they are required to exchange their foreign USD into Argentinan Pesos with a very unfavorable exchange rate.
From practical standpoint, most common NAT setups come with "default deny incoming" firewall, and systems have relied on this fot a very long time.

I hope that IPv6 is rolled out to homes, most ISPs would do the right thing and set up customer routers firewall in "default deny incoming " mode. Otherwise, the number of worms would increase a lot.
It's not a leap, considering his group had already been tied to the 1993 WTC bombing by 1996[0].

This reminds me, I've always been curious that in the year leading up to the attacks, the Taliban was a frequent feature on ABC News. Mostly for their defacing ancient historical sites from what I fuzzily remember.

0: https://www.state.gov/1993-world-trade-center-bombing/
Here's the `modern` stack I would use. but before jumping to names directly, why modern and why not battle tested react-materialui or bootstrap? Because the stack I am explaining below 'actually' solves some major problems.

- If you care about SSR then definitely either NextJS or remix.run

- If SSR is not the priority then STAY AWAY FROM REACT. Creating the complicated UIs in react is easy, but refactoring is hard. React on a big project is like point free code with ramda or lodash/fp. you write code, compose and everything is working and then you realize you missed something, so you go back and check your entire UI is a chain of many smaller, intertwined components and it's too late to refactor now. Hooks and global state management (redux) is another huge mess

- So if not react then what? That you will have to evaluate yourself.

- Vue is notoriously popular in open source community, and have often proven to be a reliable framework, especially with Vue3 you get benefits of performance + DX both. whats wrong with vue? Lots of `this` usage, vue specific directives, directives are not expressions but strings.

- Angular is worst of all. bad docs, bad DX, extremely bloated. OOP oriented, I would stay away.

- Svelte? yeah it's like Vue + React child. A lot less intuitive than either. plus community is smaller than any other framework. what you get is only and only performance, comparable to Vue.

What stack I would use:
- SolidJS (haven't used it, always wanted to try)

- If you are going with nextjs/remix/react Mantine-UI for components

- If you are going with React (CSR), chakraui with custom CSS. Good DX.

- Graphql + a lot of typescript ecosystem for large amount of codegen. the less you type it yourself the better
Violating the cosmic speed limit is not only not a "perfect model" it's an atrocious model. Wouldn't you agree? It's a model that incorporates hard contradictions to itself.

You are saying I'm a lay person? You nailed it. I'm quite curious though about what would be so "advanced" that pop-science writers would not want to at least allude to it, since just Doppler redshift observations seems like not such a sturdy foundation, especially without anything else buttressing it!
The embedded video is in a simulator. The article contains no pictures or video related to a real world deployment.
> Karl Fogel shows a good example how issues like this should be treated

Didn't this issue (n8n) actually get resolved favorably (open-source -> source-available) while the "how issues like this should be treated" was resolved (by the maintainer) by basically saying "fuck off, we will keep lying"?
Agreed. When writing my code editor I started off with a lot of UI-related state and logic in the UI (Svelte) components, things like keeping track of what tabs are open and editor state within the tabs.

Quickly realised there was gonna be a lot of grappling with Svelte as the complexity grew: figuring out what component structure to use for passing data around efficiently and ergonomically, passing events between components, using Svelte stores for global state and figuring out how to update and subscribe to them from non-Svelte code, etc.

Now the Svelte code is a thin wrapper and the app can run headless. I feel like it would genuinely be fairly easy to plug a totally different UI onto it.

Each Svelte component basically stores copies of the state it's interested in, subscribes to events from the objects it's interested in, and calls methods on those objects in response to events. This comes with a bit of extra boilerplate vs. more tightly integrating the UI logic with Svelte but the almost complete lack of cognitive overhead in this part of the code is well worth it.
The state doesn't need to do anything at all. If people are drinking themselves to death, that is within their rights.

I'm pretty concerned with how utilitarian and authoritarian our populations are getting. The state should be the last tool we reach to, and only for the meditation of severe and direct negative third party externalities (i.e. reasonable case for laws regarding drunk driving).
If it is in good faith then let me respond (albeit quite late). I've also learned "the hard way" how to behave around people who experience psychosis by taking care of multiple friends at various points in time. Some people get violent, some don't. Those that don't generally will almost never get violent -- their brain seemingly just "doesn't have that pattern", so when their consciousness is starting to hit random buttons, it doesn't often come up as an option. People that do get physical (or heavily paranoid) have the potential to go violent, and that must be kept in mind for your own safety. It's obviously a lot more muddy than that but it's something to know.

I also know a nurse in a psychiatric clinic (the harder kind), he gets bit so much they have special vaccines (?, or some other kind of medication) to protect him against illnesses that can come from a human's mouth.

I don't believe the above reactions that I have learned are trauma, it's just the rational way to act when you've seen literal examples of what can happen.
For the CSS nerds out here, cross-browser compatibility dictated the split in two rules. The following rule:

news.ycombinator.com##html:style(filter:invert(100%) hue-rotate(180deg); background: white)

works great on Firefox, but leaves the borders white in Chrome. Chrome applies the background directive AFTER the color inversion filter, while Firefox applies it BEFORE. On Chrome, you should use instead:

news.ycombinator.com##html:style(filter:invert(100%) hue-rotate(180deg); background: black)
The Game Changers.

It's fine if you don't care about the animals but it's not fine to not look after yourself. This explains why eating meat is not a good idea and it does it without preaching.
Nice try, Django core developer... :p
HA is overrated, i'd much rather go for a low mean time to repair.
Backups, reinstall, ansible playbook is my way to go if hardware fails, which is quite rare to be honest. HA goes beyond hardware in terms of "electricity, internet connection, storage, location etc.., IMO people quite often underestimate what it means to have real HA --> second location with identical setup to shift workload or even have active-active instead of active-passive.
i have an intel nuc as plain debian server with containers on it.
2 raspberry pi's(act as loadbalancers with traefik and authelia on top) and a hetzner vm all connected through wireguard.
All is configured via ansible and i rely on LE certificates to connect via https or directly via wireguard vpn to http if i want it only exposed via vpn.
encrypted backups are copied via wireguard to an offsite storage box.

full down to back online if hardware is not damaged is less than 15 min.

it is very easy to do and rock solid, unattend-upgrades does the trick.
i tried almost every combination and even though i am a k8s user from version 1.2 onwoards the complexity for k8s at home or even vsphere is too much for me vs. this super simple and stable configuration i now have.
That is an extremely difficult film. For me it was on par with watching Schindler’s List.
Is that a Starbucks pun?
I'd add to try using sveltekit.

Typescript is already supported when you set it up using the documented "npm create svelte@next".

It has cool routing, backend etc but even if you don't care about any of it, you get free hot reloads. And with the new version, you can create it as if it was your average svelte app, just avoiding + in file names and using +page.svelte as your main entry point.

For styles, if you care about styling a bit more than default styles (mvp.css or bulma/bootstrap/similar), I'd recommend using tailwind's better clone windicss, which has great svelte integration (including editor extensions for autocomplete and highlight), and writing styles is quicker than using normal css.

You can also use scss/sass/similar in style blocks, you only need to install node-sass and set "scss"/"sass" as the lang of the style block.
It's no longer considered a last-resort measure. Cirrus training now says to consider it as a first resort.
The question might be: which Macbook might your prospective usershave? For that reason I'd go with something low spec, maybe even a refurb from https://www.apple.com/shop/refurbished/mac .

(To translate back to the Windows world - if you were making an app for Windows you'd want to make sure it works on the cheap stuff at Best Buy, not just a high-end Dell XPS with 16G RAM, because most users have a cheap thing).

If your app works on a lower-end machine it should work on a higher-end one. You can run and test an Intel build on an ARM machine, you can't run and test an ARM build on an Intel machine.

In the event that your app only runs on high-end Macs - for example if it's an opportunistic port but you don't have the resources to work on Mac performance - you'll probably want to think about how to message that, before you reach the point of people downloading it and becoming loudly disappointed.
You sound like the exact target for Malloy, which was posted to HN recently:

https://github.com/looker-open-source/malloy
Feel like the constraints-based layout is not the right design of constraints. I don't know if there is any research on type based (constraints) layout. How to type flex layout in composable way, could use some vector (matrix), and knapsack kind of algorithm. A child component spec should have some layout constraints to conform.
Valley Uprising is about the history of rock climbing in Yosemite Valley: https://www.imdb.com/title/tt3784160/

I've rewatched it several times and love how they blend archival footage, interviews, and illustration to show the history of rock climbing.
Most SQL dialects accept a positional or a direct reference to the column name. “1” represents the first column created by the select statement, “name”.
I started as a philosophy major and switched to history and economics for this exact reason. My philosophy classes became incredibly disconnected from reality and ended up being endless arguments about frameworks and formalisms, but without the rigor of mathematics outside of formal logic. I still loved my philosophy classes, but I'd recommend anyone studying it as their first undergraduate degree pair it with something more concrete.
Based on the preliminary report, it seems like bad weather?

https://aviation-safety.net/database/record.php?id=20220909-...
I disagree. They are seemingly rhetorical questions, but the answers to those questions are not immediately as obvious as they are implied to be.
Modern version of Albatross seaplane in 2025
I bet such organization would be fine with no internet. Just good old trusted newspapers and TV broadcast!
I mostly agree with what you said in regards to housing, but the iPhone mini is a bad analogy. It wasn’t a low end model, it was a mid/high end model with a small screen, and apparently there’s a vocal but not nearly large enough minority that likes small devices. The iPhone SE is the low end model, and it appears to be selling quite well.
That's the key finding. And while "no effect" may sound harmless the Discussion section of the paper highlights all the ways having a popular ineffective solution is actively harmful to people with dyslexia.
Time Management for System Administrators (2012)
I don't think that would work well with the existing TLDs, where domain names often have meaning other than as just a domain name, and there is often more than one person or organization that would want that specific name.

Maybe make a new TLD specifically for infinitely lasting names, say .permanent, and make all top level names under that be 128 bit numbers in some text format randomly generated when you register the domain such as hex or base64. E.g., f560618f355b0ddf560456d41d635e3d.permanent or 9WBhjzVbDd9WBFbUHWNePQ==.permanent.

With those names it doesn't matter that they get locked up forever with the initial registrant.

> As a compromise, perhaps you could charge a nominal fee for domain name ownership transfers.

When the name is generated also generate a public/private key pair and associate the public key with the name at the top level servers. Someone is considered to own the domain if they can prove that they have the corresponding private key.

The top level would allow someone who has the private key to ask for a new key pair to be generated to replace the current one.

Want to transfer ownership? Give the new owner the private key and they can use it to do a key change.

This should allow making the top level service entirely automated and cheap to run.
Agreed that SQL lends itself to spaghetti. However after working with it for 25 years both as a developer but also collaborating with analysts and data scientists, I have to say I appreciate its basic declarative nature and remarkable portability as it has expanded into distributed databases.

For me the value of being able to walk up to an unfamiliar database of widely varying tech and start getting value out of it immediately is the killer app. Macros or other DB-specific extensions would be useful at times, but I’m not sure how much they would enable solving the messiness problem in a generic way that reshapes the paradigm more broadly. My instinct is the messiness is a consequence of the direct utility and trying to make it nicer from a programmerly aesthetics point of view might be hard to sell. It’s not like SQL doesn’t have affordances for aesthetics already (eg. WITH clauses).
What’s the target market?

Holiday makers?

People travelling round the world?

People emigrating?

People travelling for work? CxOs? Salespeople? Rich world managers checking in on offshore manufacturers? Their employers?
The British Empire certainly did some awful stuff. Anyone who thinks the British Empire took over other countries purely for the benefit of the locals must be a bit dim. But I'm not sure 'genocide' is a fair accusation. Certainly large numbers of Indians (and Irish and others) died due to their callous policies (e.g. Bengal and Irish famines), but I'm not sure that classifies as genocide.
While the official report on the reason will probably not come out for a while, there is some speculation that it was due to convective activity (thunderstorms) in the region. Someone on the Cirrus pilots forum looked up the weather at the time of the incident, and it looked like there was some decently heavy precipitation along the approach path.
We've already given it more than 50 years.
I never said you did. I'm asking you to quantify the costs because all engineering and ops decisions involve tradeoffs. Just because something incurs overhead, or is on of several solutions, it doesn't mean that it's bad. It's just an additional factor for consideration. So what are the actual overhead costs?
> One occupant was seriously injured, and two of the three occupants received minor injuries.

https://aviation-safety.net/database/record.php?id=20220909-...
Thank you so much for your comment, very helpful!

I just registered notmuchjs.info and plan to put this organize this info and put it up on github pages once I get an hour or two
I can't believe that at time of this writing, only a few other comments are mentioning VIEWs! Like that is this dude's exact complaint!

smh...
Couple of random ones I highly enjoyed recently:

- Feels Good Man -- story of the innocent illustrator behind Pepe the Frog and how the internet ruins nice things

- War Room (1993) -- fly-on-the-wall doc of James Carville during the most intense period of Bill Clinton's election campaign (amazing "pre-internet" energy)

- Downfall: Case Against Boeing -- all in the title

- Cane Toads: An Unnatural History -- hilarious story of the introduction and unintended over-multiplication of cane toads in Australia

- The Man Who Skied Down Everest -- story of a Japanese alpinist plus a team of scientists and 800+ sherpas and their mission to support him skiing down Everest from near the peak
Nordstream 1 is off.
One tower stood for another hour, the other for almost two hours. You can evacuate a lot of people in that time.
In the U.S., poor people prey on each other in their neighborhoods more than rich people do in theirs, and theft causes stores to close. Less law enforcement after the death of George Floyd has accentuated these disparities.
The nuclear policy America needs
In Hasidic Enclaves, Failing Yeshivas Flush with Public Money
It is the case, not too mention v8 pulls in an extremely expensive c++ compiler in the SDK while quickjs can compile with tinycc.

Open source is not enough anymore, "lean" open source is the way now, SDK included.
We have some ideas, of course. The rough idea is: surround the reactor with a lithium blanket. This gets bombarded with neutrons, breeding fuel and heating the lithium, which transfers its heat to coolant to spin turbines. The devil is in all the engineering details, like: how do we make alloys to deal with neutron bombardment/hydrogen embrittlement, what's the optimal geometry to capture flux while being serviceable, etc.

Much of that work can and is researched in parallel, but there will be inevitable integration hell that has a burning fusion reactor core as a prerequisite.