skysight-inc/HackerNews huggingface dataset:
You're making my point stronger. The EU Court on Human Rights made those rulings based on the following provisions of the EU Convention on Human Rights:

> Article 8 – Right to respect for private and family life

> 1. Everyone has the right to respect for his private and family life, his home and his correspondence.

> 2. There shall be no interference by a public authority with the exercise of this right except such as is in accordance with the law and is necessary in a democratic society in the interests of national security, public safety or the economic well-being of the country, for the prevention of disorder or crime, for the protection of health or morals, or for the protection of the rights and freedoms of others.

> Article 12- Right to marry

> Men and women of marriageable age have the right to marry and to found a family, according to the national laws governing the exercise of this right

Even a dedicated textualist could find the above provisions ample justification for finding a right of same-sex couples to marry. Instead, the EU court adhered to a traditional definition of "marriage" and only found a right to civil unions and to mutual recognition across member states.

The U.S. Constitution, by contrast, contains no remotely similar provisions on which to premise a right for same-sex couples to marry. Yet, five justices, including a Reagan appointee, did just that. The U.S. Supreme Court is vastly less respectful of our democratic process than its counterparts in other developed countries.
This is turning into a complete train wreck and a case study on how not to communicate with your customers.

For those of you that haven't been following, Heroku has been adding non-update updates to this security thread over the last couple of weeks, which began with the announcement that some (or maybe all) of their GitHub granted access tokens had been compromised: https://status.heroku.com/incidents/2413

Now, weeks later, we're hearing that all account passwords are being reset, and for some reason if you have been using an HTTPS-style log drain that you should reset any secrets related to it as well.

Heroku needs to come out and clearly state what they know about this situation, and more importantly what they don't know -- which is starting to sound like the answer is "a lot". It's not even clear they know how this all happened -- whatever door was left open might still be open. So if you've gone and rotated all of your application secrets (which you probably should do), be prepared to rotate them again when this is all over.
HDF5 has some limitations that make it suboptimal for cloud based storage systems.

Zarr overcomes these limitations for array data and Parquet overcomes these limitations for tabular data.
So employers in Colorado won't be allowed to refuse to hire people as bookkeepers just because they were previously convicted of embezzling while working as a bookkeeper for someone else in the past?
Nice. I've been stewing on a similar idea but that finds correlations in equities with commodity futures.
If you pass new props, it swaps out the whole instance of the element in the document. Probably.
Related:

Macchiato – A way to build Node web applications using ClojureScript - https://news.ycombinator.com/item?id=15978612 - Dec 2017 (66 comments)

Macchiato: ClojureScript on the Server - https://news.ycombinator.com/item?id=13096325 - Dec 2016 (19 comments)
Thank you, these gave me some ideas. Seems like a safe first step is distilling my commit history into projects, features, and how it helped the business.
This email arrived in the evening but this morning I received the hard word to switch to AWS - NOW! - instead of wasting time with Heroku. Several orders of magnitude more complex but probably the right answer.
Our original business model (get paid for making hires) was too early, so our lead engineer said “why don’t we put out a tip jar?”

Remarkably, that worked!

Most people tip, typical tip is $40.
Surprised this news reached Hacker News. The major was kind of lazy. We used to joke we didn't have a mayor. In summary, he won't be missed.
It's a female dominated industry. It should be seen as a problem just like it is for male dominated industries.
>and a terrifying demonstration that we need to grow the hell up with respect to data privacy

Once again, "conspiracy theorists" were right. I'm beginning to think the governments of the world are reading them for ideas.

>The fact that we don't have a standardized way of blessing data with varying known levels of privacy, checked and enforced by law, is kind of ridiculous in 2022.

Sure, and then as soon as that happens, someone who has patented/copyrighted the process coincidentally is handed a government mandated empire worth millions in licensing fees. Look into ICD-10 codes if you need an example. It's the classic college professor scam where they write the textbook and force everyone to buy it.

>It shouldn't be up to the CDC to act counter to their mission.

If CDC can't do the job without violating 4th amendment, it shouldn't exist. It's not a "private company" and the bill of rights exists for a good reason.
Tighter integrations in the server market.
> This is not hypothetical.

Then you should provide a link to a reputable source. Not sure how a state government in the US could pass this, let alone enforce it
Which specific limits on freedom are necessary? What are the criteria for determining necessity?
SLS is a spiderweb of already built old engines that somehow cost lots of new billions
“A crypto executive…” not “the crypto executive”
But you already have to take care of a nuclear waste depot, nevermind the nasty chemical stuff that never degrades and has to be stored forever.

It does not really matter how big the caverns are where you store the waste so any additional nuclear material stored is basically free.
Colorado Legislature Passes HOA Foreclosure Reform Bill
> THEY MAKE RECOMMENDATIONS

Ahh, I see where the confusion is. They actually have authority to issue legally binding orders.

"To help prevent the spread of COVID-19 and help our country cope during the pandemic, CDC has occasionally issued legally binding orders and regulations."

https://www.cdc.gov/coronavirus/2019-ncov/cdcresponse/laws-r...

Not all such orders are listed on that page. For example, "CDC Director Dr. Rochelle Walensky today signed an order determining the evictions of tenants for failure to make rent or housing payments could be detrimental to public health control measures".

https://www.cdc.gov/media/releases/2021/s0803-cdc-eviction-o...
I’ve been cooking out of The Wok and it’s also fantastic. The technique sections have been super helpful!
multiple salts can be stored, no? and they can still figure out the same password. Google does the same, even going back multiple passwords in the past ("this password was used previously X years ago").
This is effectively saying that they're exposed to root or the owner of the PID, which is the same story as storing secrets in files. Root also has other ways to get secrets out of remote processes.
True, but as far as cloudflare goes - it doesn't explain why plain, probably cached, GET requests have to be behind a captcha. If that's really an issue, can't they save it for POST requests and other non-static endpoints.
I think this is an interesting way to generate migration scripts at design time, but I wouldn't trust auto-migration code in production that migrates from arbitrary schema to arbitrary schema. Take migrations that require copying the entire table - this could be fine for small tables, but extremely expensive for large tables. If disk space is a concern, this will also use 2x disk space! I at least want any such operations to be obviously visible at code review time, so the team can discuss any performance implications before we ship such a migration.

Our team uses a rigid workflow to maintain the SQLite schemas for our mobile and desktop apps:

1. Generate a new migration. This creates ${SCHEMA_VERSION}-migration-name.sql, where SCHEMA_VESION will be the PRAGMA user_version after migration. We also generate a matching ${SCHEMA_VERSION}-migration-name.test.ts.

2. The developer updates the migration file to do the thing. This part we could replace with declarative table diffing as in the article, which would be cool! The developer also fills in the test. Our tests typically write some rows to the DB at SCHEMA_VERSION-1, perform the migration, and then make assertions about how the rows look after the migration.

3. When the changes are ready for review, the developer runs a command that packs up all the migrations into generated allMigrations.{json,ts} files, along with an auto-generated "fast-forward" migration that is just the final database SQL dump, and a JSON description of the expected end result schema.

4. On end-user devices, at app boot we read PRAGMA user_version and apply the migrations transactionally in order, to the latest migration. At the end, we assert that the schema in the database matches the expected schema. If the database is new, like on a fresh install, we apply the fast-forward migration instead.
That's shrinkflation of middle class, basically. At this pace, middle class in 50s will be your own tent under a good bridge.
Or chaining it even further for copying a null-terminated string. The assignment operator returns the same value that was just stored, so it can be used as the conditional on a while loop.

while(*dst++ = *src++);

Incredibly succinct, ridiculous powerful, and way too easy to overrun array bounds.
That's what I don't understand as well.

Where is the conflict of interest in the case of the mayor of Lima? Why is there such a rule against that?
How would you check that across accounts if you had per-user salts though?
In the beginning there was the command line. A keyboard input to a type on paper output. Then UNIX. The first editor was 'ed' (edit). It was line based, designed for a keyboard onto paper output. It was enhanced to become 'ex'.

When the happy hackers at UC Berkeley were porting UNIX onto VAXen (becoming BSD Unix), CRT terminals were available, notably the DEC VT-100 and other less expensive ones. These terminals had commands that would move the terminal cursor around the screen, allowing a editing program to modify the 24 (or 25) lines of 80 characters on the display. But the terminal commands were DIFFERENT. So the configuration file TERMCAP and the C library libcurses were created.

Then 'ed' / 'ex' was expanded to become 'vi' (visual, not six). Note that the 'ed'/'ex' commands are still there, invoked by the ':' command. Now there was a full screen text editor that worked on different CRT terminals.

This was all before UX design existed. It evolved. 'vi' was a giant leap up from a typewriter editor.

(We don't need no stinkin' mices)
This is exactly why the CDC should not exit. Their mission is at loggerheads with liberty.
In this particular case the opinion explicitly stated that the constitution does not provide a right to privacy.
Man this actually looks pretty awesome, despite the weird placement of the hard modifier keys. Wish updates were guaranteed
ADHD is only a difference in degree not in kind. But that degree can still be significant enough to be crippling.
It's funny - in the UK I think we'd say the middle class is getting smaller but the standard is staying the same, while in the US you look at it as the middle class stays the same size but the standard falls. Different approach to social statistics!
Sure but sometimes you just want to get the pothole outside your house fixed, which requires being able to construct (even for just the short term, privatise that road if you) systems and incentives that work for real problems, which in turn requires people to (regardless of trust) get their arms dirty which I think is unlikely if you have everyone trying to propitiate to the ghost of Ronald Reagan.
I think it's trying to stay fairly close to C, with additional features selected judiciously. Systems programming was identified as an important design goal (e.g. having close control of memory layout).

See also:
https://en.wikipedia.org/wiki/Go_(programming_language)#Omis...
>It is all but gone now, today my friends teen-aged kids are about fitting in,

Wait, doesn't that sound like the same thing? Presumably some kids are still non-conforming, and they are still the minority (because most kids of all generations have prioritized fitting in).

Be very wary of survivor bias when looking back in time, especially when there is a risk of nostalgia. There was plenty of popular garbage in the 70s and 80s, there is plenty of good music being made now. The only real difference is that we have yet to apply the "is this good enough to keep around" filter to modern culture.
>a sink should generally not overflow from just being left on

I once thought all bathroom sinks had a little drain hole in the side to prevent overflows. But not all do. (in places I've lived in my area of the US)
What kind of God are you to judge others for their choices? Do you equally judge those who miscarry, or who give stillbirth, as murderers? Why not?

As for not being torture or a disease, it has killed billions through the ages.
Same here. But I wouldn't use the word 'holographic', since it's now too associated with junk science and New Age crap. Even if it does happen to nicely capture the meaning.

Put simply: if you have two related concepts, say "car" and "truck", then it makes a lot more sense to me that they'd be represented by similar weights among a collection of neurons, than if each concept got its own single neuron (or handful of distinct neurons scattered throughout various functional parts of the brain.) If you did that, you'd need to explicitly encode the various similarities and differences. It would take time for priming to travel from one thing to all the related things. There would be no or limited redundancy. Forking off a concept (eg with language, learning a synonym) would have to be some explicit process.

With an aggregate representation, you get all of that automatically. When you're thinking "car", you're 70% also thinking "truck". You can evolve your understanding freely without breaking anything, you can split and merge representations, etc.

It kind of seems obvious to me, which is no proof that it's correct. I'm reading Kahneman's "Thinking, Fast and Slow" right now, and it's a brilliant book yet I feel like this representation would convert many of his puzzled observations into unavoidable consequences.

Separately, I think there's less of a distinction between memory, recall, and actual experience than this paper makes out. They feel the same because in the brain, they are (mostly) the same. And there's more of a distinction between memories of different things. I expect to find very different brain regions involved in memories of pain vs movement vs vision vs procedural knowledge etc., because much of the memory will be in the neurons directly linked to the relevant sensors or actuators. (As above, the memory is the experience, or at least it overlaps substantially.) Sure, there will be overlap across all those, but that's not because it's the One True Memory Region, it's just that there's a generic component to any memory (or rather, anything that we would refer to as "a memory".)
I've actually started working on something very similar:
https://github.com/tmccombs/ssv

So far it's just a python library, but I'm planning on adding editor plugins at least for vim, vscode and maybe emacs, libraries for additional languages, and maybe some cli commands for it.

One distinction from the OP is the delimiters also include a tab (for fields) or newline (for records) by default (but not in "compact" mode). That has the benefit that the files are at least readable with editors and pagers that aren't aware of the format.
Those were openly acknowledged to be loss-leaders even before COVID. But I wonder how long they're going to stay with their current pricing, with food prices soaring across the board. End of an era, probably.

And I have no doubt they're what holds Sam's Club pricing down too, as soon as they bump their prices so will Sam's.
Their FAQ says it's not recommended to use after 11 weeks of pregnancy, however there is nothing that prevents a woman from using it anyway along with the massive health risks that come in doing so after 11 weeks. I guess by them burying the warnings in the FAQ they are covered legally.
I always thought the blacklistable credentials was a cool approach - we're you prove you control an ip but dont reveal it. https://www.cypherpunks.ca/~iang/pubs/blacronym-wpes.pdf
Microsoft tried to convince all C++ developers to switch to C# and completely and utterly failed. It was amusing to see how quickly they switched back to supporting C++ after years of pretending that C++ had no future.
Probably the best "debugging in space" story is Don Eyles hacking the Apollo moon lander program that was in "core rope ROM" to work around a hardware failure on Apollo 14.

It is findable online, but he published a book "Sunburst and Luminary" (Fort Point Press, 2019) about the whole process of getting the moon landing code ready in time to use, and the hack.

As I understand it (I just got the book, haven't read it yet) the Apollo Guidance Computer, one each in the Command Module and the LEM, was programmed by Margaret Hamilton (inventor of Software Engineering as we know it today) with a real-time executive and interpreter emulating a saner machine, and Eyles coded the landing to the interpreter. Because it was interpreted code, it was patchable, and he came up with a patch on the fly that the astronauts punched into the AGC by hand, and saved the mission.

Margaret Hamilton's real-time executive itself saved the day when Apollo 11 crew left some extra stuff turned on, by accident, that the system had not been tested with and that burned excess CPU cycles during the landing. When it trapped a scheduling failure, it checkpointed important state and was able to resume the important tasks where they left off. That happened several times during the landing.
I live in France and let me tell you: CSV is not good enough.

What about France you say? The decimal point is a coma, and to avoid confusion, the list separator is a semicolon. So "1.5, 1.6" becomes "1,5; 1,6" when localized. And if you think it is terrible for CSVs, well, it is worse than that.

If we all used RFC4180 consistently, it would work, but of course, that would be too simple. Some software insist on localization. So unless you need to know the software and locale that goes with that CSV. In the most simple case: you can treat both comas and semicolons as separators and it will work for reading, for writing, you have to pick one that the target software hopefully understands.

Hell starts when you have decimal numbers, because sometimes, you get exported CSVs where the coma is used both as a decimal point and as a separator. It makes the number ambiguous and your file becomes useless. It can result in data loss (personal experience). For example "1,2,3" may be [1.2, 3] or [1, 2.3]. And even without that, you still have to guess if you are using points and comas or comas and semicolons.

And of course, there the quoting/escaping issues every country has. Good thing the RFC has clear rules, I heard you can even find software where they are properly implemented. Of course, in France we also have the added bonus of questioning whether or not comas should be quoted since they are not the localized separator.

And character encoding? Of course it is a mess, as with every text file, but CVS makes no effort to help, is it UTF-8? Latin1? I have seen both, and I have seen files mangled because they were opened with the wrong encoding. Also, line endings should be CRLF, for those who care.

CSV as defined by the RFC is good enough, the problem is how it is used in practice.
Thanks for saving me the time
I use checkboxes with things I hope to accomplish today. I start that list before I go to sleep the night prior and continue to fill it out in the am if there’s any updates. Then I try to check each of them off. I’m bad at keeping to a schedule but it gives me a huge dopamine rush to check off each box as I complete items.
So if you are poor and hit me in your car and you don’t have insurance, who is going to pay?
They aren't "forced out of the market". That's just made-up.

And the animus against standard OS upgrades is not particularly convincing, to me at least.

The value of Intel Macs is holding up just fine. I can go sell my 2019 Intel MBP and still get a lot more out of it than a PC laptop of similar vintage. This has of course been historically true of Macs, as well, as even a cursory investigation will reveal.
> That's a nightmare to try to edit yourself in a text editor?

You just need a text editor that can support thia format.
https://flux.ai provides a similar module based approach to design

It doesn’t just cover schematic design but also PCB layout. The later which I am not sure Jitx can do
Depending on the complexity of your computations and state, what you just described can basically become unusable. For example, an app I work on implements a spec which:

- Models state as an arbitrary DAG

- With arbitrarily deep dependency chains

- Which may trigger dependent nodes based on only subsets of their state

- Based on computations of arbitrary XPath expressions, sometimes containing non-native extensions; these can be expensive whether implemented as a hybrid wrapper around native XPath or fully in userland

- Which in turn may trigger recomputation of their own dependent nodes

A naive implementation of this according to the algorithm you described will cause real world usage to block sometimes for several seconds until the app becomes responsive again.

Being able to have greater control over when to commit state and when to render intermediate state are crucial to usability for this app. Being able to defer the entire computation for state without a path to an associated view is even better. Being able to batch state -> render updates based on priority even better still. All of this can be accomplished with React’s APIs, but it certainly wouldn’t be the default behavior. And it’s all from a real world use case where SolidJS—which has a similar DX to React but significantly better performance, and which I’ve been prototyping for gradual adoption—also needs more optimization than its dependency tracking alone can achieve.

Even trivial demo apps with well designed pre-hydration state (note: already optimized beyond the default) and otherwise find performance at runtime can suffer significant lag between LCP and TTI by running far too much code for stuff that’s nowhere near needed for immediate interaction.

Granted in most cases this tradeoff is reasonably acceptable. In many cases it’s not. Prematurely optimizing it isn’t a great idea, but there’s a wealth of room for optimizing when it’s valuable to do so.
We had some legacy applications running on Heroku. We're porting it over to our EKS infra over the next couple weeks. There has been no explanation how the Github keys got leaked and I can only assume the worst.
I'm not afraid of marketing flyers. I can handle crap like that. Highly Targetted Advertising, as annoying as it is, doesn't threaten to lock me up if I don't purchase something.

But I can't stop an inadequate power hungry government bureaucrat threatening me and my family over whatever because they want to feel important or powerful over others.
This gets brought up a lot but I always wonder were the other 2/3 happier after they left? They sounded like a bunch of militants trying to politicize things needlessly.
It’s amazing how aggressive conservative states are at enforcing their laws across state boundaries, but then turn around a cry states rights whenever things are the other way around.

Almost like they’re a bunch of jackbooted theocratic hypocrites.
> Which specific limits on freedom are necessary?

That's the eternal question. Not just for disease control, but for everything.

> What are the criteria for determining necessity?

In a democracy, ultimately: elections.