skysight-inc/HackerNews huggingface dataset:
Everything is a Remix: https://www.youtube.com/watch?v=nJPERZDfyWc&ab_channel=Kirby...

"A child never writes his own alphabet. A seed does not grow, it needs soil, water, and radiant energy. A sailboat does not sail, it's shoved by the wind. Nothing in nature is self-activating." - Jacque Fresco

We claim to be self-made, to be "born that way", yet we all have accents.

But not just accents of speech, accents of action (the surfer learning to skate will skate with a 'surfing accent': https://en.wikipedia.org/wiki/Z-Boys), accents of thought (many of us are familiar with the archetypal poor person in a difficult environment which imprints a 'roof could fall in at any moment' mentality, who then becomes rich yet remains in that frugal mindset), accents permeating every atom of behavior we exhibit.

Why are we drawing a line around speech and saying "accents only develop here... everywhere else, we can be totally original or totally genetically talented!"

The mind is fashioned by what it feeds on.
Given that hearing aids can be (blindingly) expensive, this can be a good thing. However, check the small print about legal liability concerning damaging hearing due to incorrect settings. I assume this can be treated as similar to headphone/earphone use, but it might be necessary for the suppliers to create/use a different term to avoid any of the legal or social ramifications of the term "hearing aid". They certainly want to offload all responsibility to the buyer.
> This is a new area of development, and we’re all learning.

Being a new area of development doesn't release you from your obligation to make sure what you're doing is ethical and legal FIRST.

> I’m personally spending a lot of time chatting with developers, copyright experts, and community stakeholders to understand the most responsible way to leverage LLMs.

And yet oddly nowhere did the phrase "I reached out to OP to discuss with with them" appear anywhere in your response." Nope. Being part of GitHub's infamous Social Media "incident response" team was more important than actually figuring out what was going on.

You don't even say that you will look into the situation with OP, or speak to them.

waves to all the github employees who will be reading this comment because someone on Github's marketing team links to it
> I’ve noticed a troubling tendency in the JavaScript world recently, particularly in the React community. That tendency is for people to suddenly “discover” that decades of best practices somehow don’t apply to them anymore.

lol, this is just a problem with developers in general. Between burnout and hiring bias they trend young. Information and best practices struggle to get passed down across short generational overlaps.

The number of times I have seen the same bad ideas resurface over and over in my twenty year career is just insane. Document stores were the rage, then they were bad, then they were great again, and I think we’re cooling down on them again.
DIY Serverless ClickHouse on Deta Space
True! He’s making a bold and false claim.
Elaine literally says that she hates men on the show lol.
This response expresses some of the things, that are to criticize about MS' Copilot project. But also I don't like the instant attempt to subtle discredit the report by dropping something like "I don’t know how the original poster’s machine was set-up" in the first (or second, if you want to be technical) phrase.

First consider that you made a mistake yourself, _then_ ask, whether the fault could be on the other side. I really dislike this high-horse down-talking tone. Maybe it was not meant to sound like that, maybe this kind of talk has become a habit without noticing. Lets assume that, giving a benefit of a doubt.

Onto the actual matter:

> If similar code is open in your VS Code project, Copilot can draw context from those adjacent files. This can make it appear that the public model was trained on your private code, when in fact the context is drawn from local files. For example, this is how Copilot includes variable and method names relevant to your project in suggestions.

How comes, that Copilot hasn't indicated, where the code came from? How can it ever seem, like the code came from elsewhere? That is the actual question. We still need Copilot to point us to repositories or snippets on Github, when it suggests copies of code (including just renaming variables). Otherwise the human is taken out of the loop and no one is checking copyright infringements and license violations. This has been requested for a long time. Time for Copilot to actually respect rights of developers and users of software.

> It’s also possible that your code – or very similar code – appears many times over in public repositories.

So basically it propagates license violations. Great. Like I said, the human needs to be kept in the loop and Copilot needs to empower the user to check where the code came from.

> This is a new area of development, and we’re all learning.

The problem is not, that this is a new development or that we are all learning. That is fine. Sure, we all need to learn. However, when there is clearly a problem with how Copilot works, it is the responsibility of the Copilot development team to halt any further violations and first fix that problem, before letting the train roll on and violating more people's rights. The way this is being handled, by just shrugging and rolling on, maybe at some point fixing things, is simply not acceptable.
Can you source some peer-reviewed research that shows this? Everywhere I look the baseline seems to be IQ scores can't be trained save a tiny few points. And 3 IQ points don't really make a genius out of someone smart.

Free will has nothing to do with not being able to do something because physical constraints are placed on a person. e.g. A person in a wheel chair does not have more or less free will then someone who can walk. Even though the latter clearly has more freedom in a certain sense.
That was introduced during the Oktoberfest here in Munich, as there had been dozens of injuries and hundreds of people so drunk they got their license revoked on the spot in 2019 [1].

Operators didn't want the hassle of the paperwork involved with drunk drivers, crashes and followup costs, so they agreed with the city on implementing a "latency test" or other scare-offs [2]. Some of the operators already had that voluntarily activated during night time in other cities, some had to implement it from scratch, but I think they will more-or-less keep it in place.

Additionally, the potential for severe injury is way higher with a scooter than it is with a bike. Scooters run faster and are way more sensitive to steering input.

[1] https://www.welt.de/vermischtes/article201502060/Nach-Oktobe...

[2] https://www.br.de/nachrichten/bayern/oktoberfest-sperrzone-f...
This is orthogonal, because expressions can be indexed too. Of course if you see the same expression three+ times in your code, it’s begging for a name.
I went to the Guggenheim exhibit. It really made me want to design a programming language for doing wacky generative geometric art. It was really fun thinking through what geometric construction tools were used for some of the shapes etc
Are you sure? According to Statistica there were over 700k bankruptcies in the US from 2000-2020 [0]. How many bailouts have there been?

[0] https://www.statista.com/statistics/817918/number-of-busines...
A good rule of thumb is if you're worried about code being copied you really shouldn't put it on github. Even if most large companies respect copyright, that small studio in Russia certainly won't.
I agree with most of these points. They are a good starting point. I'd probably steer clear of kubernetes until you actually really really need it. ECS is good enough for most things, and a fucktonne more simple to look after.

but, where I hard diverge is the lack of metrics. Everything should be generating metrics. Logs are great, but they are crap for giving you near realtime trends.

Everytime your container gets a connection: increment a counter. Every message processed, counter. every message failed, counter. Every KB of data sent out, counter. Every service call, counter by service.

metric all the things, in a sensible, mostly automated way, with a decent schema.

Then you can combine all those metrics into a dashboard that shows your system performing against business goals.
Early in the pandemic there was a notion that the entire antivax movement was white, racist, right wing nut jobs.

Reality is quite different. The people not getting vaccinated are the people who have dealt with the government the most. They have a certain distrust after years over years of dealing with the government.

Meaning, the vast majority of the antivax hate ends up impacting the most vulnerable in our society.

Hate is bad. It's anti-human and a huge step back. It doesn't make anyone, anywhere, morally superior and it definitely isn't a marker for intelligence.

In fact, swallowing wholesale the narrative by people who have a vast history of lying(or no history of any truth/intelligent ideas) is the least intelligent thing one can do.
Hasura supports multiple data-sources and creating relationships across multiple data sources.

Sources can be databases (postgres family, sql-server, big-query currently, and as we add support for new databases) or REST APIs or GraphQL APIs.

This composition allows in a final GraphQL API that federates across different sources.

From our docs: https://hasura.io/docs/latest/data-federation/data-federatio...
Quite a claim with no source. Are you claiming that the manufacturers are making trucks with illegal headlights? Because that seems pretty far fetched. Or that drivers are modifying them? Because that is very rare.
C9 club members unite!

(I forgot it all. It's been 35 years ago last I did this and high school mostly crowded it out of my memory. But C9 was RET, that I still remember. ZX Spectrum, for me. But Z80 manual (dis)assembly nonetheless.)
This is really disingenuous in practice, though.

If public wikis were really a matter of just anyone contributing any edits they want, then it would just be utter chaos. The entire concept would collapse, under a barrage of bad faith trolling or else good-faith-but-wildly-contradictory edits.

Just as the utopian ideals of open source source generally work only when there is a corporation or foundation funding it, wikis only work when there is a power and control hierarchy. A "priestly caste" emerges, that uses wiki-lawyering and brute force determination to consolidate power and enforce a specific vision for any page.

In other words, contributing to Wikipedia or something like it is such a godforsaken task post-2010, that only the most manically obsessed and dedicated would even try. Some might argue that this is a feature not a bug, I don't know. But it is absolutely valid to criticize a wiki page, without necessarily going to war to get it changed.
After they leaked drivers licenses and other personal documents uploaded by their userbase for verification, I'd be astounded that anyone is still willing to use that platform.

See: https://www.rt.com/usa/512152-parler-hacker-data-leak/
I am going to try the fix of just changing the bit rate back and forth first, see if it stays.
Virding's First Rule of Programming (2008)
That sounds to me like picking and choosing what's okay because "opinion" and what's not because "blatant lie".
The data model fits better. The data is relational and fits neatly into a simple relational table of user_id, skill_id. I think perhaps you just don't perhaps like SQL syntax which is why a join feels weird to you, but what you've described is a 4 or 5 line sql query which anyone can understand. Additionally, you can now easily answer questions like. "How many skills does the average user have?" "Who has the most skills?" "What are the most popular skills?" etc, all likewise in trivially simple sql expressions.
I'm with you on what's impressive and what isn't. I've done considerable work on page load performance engineering in the past, getting times down to the low single-digit milliseconds as you would like while maintaining high traffic levels. I know how to make every part of the system work together to minimise response and rendering latency, which is nice for people with suitably low-latency connections, and for APIs that respond nicely in client-side applications.

Unfortunately, for myself I can't even get a ping response from the ISP upstream router in 15ms, let alone a static page over HTTPS.

None of my internet connections has sufficiently low latency - neither home nor office.

HN takes 400-600ms to load, but that's understandable due to physics. Wrong country.

I just loaded news.bbc.co.uk, which is in my country and is also well connected, and saw that DNS resolution took up to 400ms, and TLS setup took up to 650ms (though not both at the same time in a single request). Total page load time was about 2s.

Those numbers seem unnecessarily high on this connection. But 15ms is too optimistic: the network latency isn't low enough, even for a small static page.

There are a lot of people in a similar situation, living with connection latencies you would consider high, but it's all we can get.
Exceptions are the worst, except for any other way of handling errors.
Looking over your shoulder isn't part of driver's ed in the US? In Germany you'd literally fail your exam if you forget to do that even once before turning. You don't even need to move your upper body, just turn your head to the side and look in that direction and you'll cover most blind spots. They also teach you how to adjust your mirrors and how to tell they're adjusted correctly. They also do a blind spot demonstration.
Doesn't seem to be open source though. NRK has a bunch of open-source projects on github [0], but the app isn't one of them, only some support libraries [1]

[0]: https://github.com/orgs/nrkno/

[1]: https://github.com/orgs/nrkno/repositories?q=yr&type=all&lan...
corporate policy problems would be only if mutagen.exe is banned by your IT department. usually open source projects are ok with most companies.

there are issues occasionally with symlinks (especially with large node_modules folders) but most of the times nothing breaks and they are easily fixable - running mutagen sync monitor shows you things as they happen. one thing to consider is where .git directory is hosted. I personally keep git on windows side - you should make sure it only exists on one side and add an exclusion (mutagen has a parameter for that). performance wise, on SSD, an npm install from zero takes at most 5 seconds to sync (running npm on wsl2 -> files appearing on IDE).
Search Git history from the command line
I was just thinking about this. At some point, it seems like companies that want to innovate will just have to break laws and hope public support for a new, better product gets them off the hook somehow. Sounds crazy, but the thought arrived in the context of "how do we do health insurance better?"

I was picturing something like what we've seen with marijuana, where laws change at the state level while DC looks the other way.
I suspect the main issue is getting discovered. Without filters like "no ads" or "no in-app purchases" in Play Store, it's hard to see how Google would ever organically bubble results for such an app to the top (since Google Ads is by far the most popular and there are definitely financial incentives to promote those apps over more privacy-conscious ones).
It is a well known fact media outlets in France are terrorised by the german police and never would date to criticize it. Same for all other EU members of course.

Seriously how do you explain there is a single media outlet peddling this point of view?
How about the using nosql by default to enable rapid development and sql when theres a need for it?

My point is that the development speed for nosql should be roughly the same as for relational databases, because you should be spending the same amount of time thinking about your data. The database you use is almost incidental. Whether you choose to create a users table in Postgres and make sure the data is valid there or whether you choose to create a JSON object in MongoDB and make sure the data is valid in the application logic doesn't matter - the hard, and the bit you should be spending time thinking about what does 'correct' mean for this set of data.

If you're creating a MongoDB table with a user JSON object, and then you just let different services manipulate that JSON however they want then your data will screw up in the future. There needs to be a robust contract between the app code and the data store that defines what the data is allowed to look like. That's where the time gets spent, whether it's in the database admin or in the application layer.

I would argue it's a bit easier to do that in a relational database but that's mostly down to experience.
One more big one related to your first point: the demographic driving Teslas is hardly a random sampling of the population, which probably impacts driving behavior _but also_ implies the driving done (e.g., where) is probably quite different from the population as a whole.
The do have a shorter lever arm.
Thanks for reductio ad absurdum baiting. And yes, these "laws" are clearly an abuse. Most of them ends up banning virtually any drawings because its impossible to assert if particular manga really depicts non-minor. Funny thing to see where burden of proof is in this particular case. Even more funny what its been almost 1.5ky after Justinian's statute.

But anyway... Why should I give up my freedoms just because of someone's parenting failures? Irresponsible parents are putting their children in danger, not the ABSOLUTE freedom of speech. Which isn't a subject of quid pro quo, really. And even not because my libertarian views on this matter, but because it simply doesn't work otherwise.
I didn't see any! Did they remove it?
Many successful comedic shows are named after their creators.

Bob Newhart had _two_ shows to his name. Carol Burnett had a show named after herself too. Of course, I'm dating myself by readily recalling those. :-)
> Gunfire, mmm, don't know. Hand-held

Guns are getting smart. https://www.popularmechanics.com/military/weapons/a30720528/...:

The U.S. Army is evaluating a scope that won’t let the user fire his or her rifle unless the shot is guaranteed. The SMASH scope is the product of Smart Shooter Ltd., an Israeli company, and could go on the Army’s upcoming replacements for the M4 carbine and M249 squad automatic weapon. The scope, or one like it, will eventually go on the Army's next generation squad automatic weapons.

(Company at https://www.smart-shooter.com/)
Imo the string thing is a bad example, as they don't really have to work that way. Storing length is another solution, but because C is C, the NUL method is quite prominent, if annoying
>People drink and drive in America because they have no choice. You can’t walk him from a bar, and even if it’s available nobody is paying $40 for an Uber when they can drive their car.

List of choices:

1. Not drink alcohol

2. Drink less alcohol, and switch to water at least 1 hour before driving.

3. Pay for a driver

4. Live where you can walk to an establishment that serves alcohol

5. Rent a hotel room nearby

And so on and so forth. Drunk driving is certainly a choice, one made because the perceived or true cost of drunk driving is less than the cost of not driving drunk.
Most people think acting like an egomaniacal jerk is what being assertive means.
I agree, but your sentence is empty: errors do not exist, they are just conditions that you dislike. Do not let your emotions affect the syntax for control flow!
You can find a happy middle ground between unrestricted free speech (of real people) and banning spammers and people who run alt accounts.

Making the system invite-only may be a requirement.
I’m sure it doesn’t have “full” feature parity, but do you really need 100% of k8s’ features? ECS is a lot simpler to work with and has plenty of features for most systems.
It's very easy to understand.

With Ansible, you first start a machine, then build a configuration on it.

With Docker, you first build the configuration, then start the machine (not a real VM, but an isolated enough slice).

The upside of a Docker image is that you build it once, and then start instantly, no need to wait for Ansible to run through steps.

The downside, but also an upside, of Docker is that you can't make persistent changes inside it while it's running, and usually you avoid such changes. You always can restart it from a known state.

Of course Ansible can handle more aspects than just application software configuration, basically any aspect at all. This is its upside, but also a downside: you can make an unintended system change along with some innocent-looking operation by mistake, and nothing will stop you, there's no separation of concerns.
Probably not? Models are trained on restrictively licensed things all the time, such as images that are still in copyright. This is generally believed to be fair use, though I think this has not been tested in court?
If you think Ansible and Docker are solving the same problem you haven’t understood yet why people use containers for deploying software.

We use them because then what’s running in prodcution is 100% the same as is running locally when testing the application.

You can hardly get there using Ansible.
Here is another: Spelling of 'Equities' in Terminal
And AFAIK an anonymous political dissident wouldn’t want a blue checkmark?

Furthermore, there can be layers of anonymity. There can be anonymous publicly but not to Twitter. That’s dangerous given that Twitter cannot protect your identity from a state actor accessing its internal systems. Thus, again, why would you want a checkmark as a dissident.
Many modern lidars absolutely can see through fog/snow/dust/rain, albeit degraded.

Blackmore, and Aeva can see through fog and dust that others can’t. Most sensors can see sufficiently through rain and snow.
Thank you, gonna check it out!
Additionally, FK constraints are a good thing, they mean that one of your users doesn't have the "Python" skill while another one has the "Pytthon" skill. You need this - and with SQL it's extremely easy to implement.
So why didn't the article's author include that in their article title "Tesla fires after hurricane raises alarm for Florida officials"?

Perhaps a (more) Tesla(s) did catch fire after Ian but that claim is not supported by the article.
I’ve done similar experiments compiling a Rust server to WASM and running it in the browser. I didn’t use HTMX, but it could easily be added.

https://github.com/logankeenan/notes-demo-spa

https://github.com/logankeenan/axum-browser
> TCP retries won't help if your backend is restarting, if failover switching is happening, if your overloaded cluster has just been scaled up to add nodes, etc.

Yeah, this is where the nuance begins.

You are correct that TCP is not always sufficient. Perhaps where we differ is that in my experience, it still helps for this to be a feature of the framework or infrastructure that the applications are running on (e.g. a retry budget in the service mesh, or a load balancer) rather than scattered around in the application itself. At some point it becomes a word game – you could say that the service mesh is also kind of an "application" itself, but the core principle is that the retries should be kept in a few simple, common places that are rarely tuned.

Otherwise, you will find that N developers who are tasked with figuring out something like this will scatter N different version of your exponential randomized delay policy all across your codebase. It is always possible to avoid this with enough code review discipline, but once the trend starts, it's much harder to say "No, you need to fix this the right way".