skysight-inc/HackerNews huggingface dataset:
Musk seems to have a very tech bro way of handling things. "Don't tell me what can't be done. You're just stuck thinking inside the box."

Sometimes you are in the box, and if you don't recognize it, you smash into it. We valorize the people who break out and accomplish great things that were thought impossible, but we never get to hear about the things that actually were impossible.

More importantly, the people who did were often more lucky than smart. Over and over we see the ones who got rich and famous screw up everything they try after that.

Musk succeeded more than once, and was surely smart as well as lucky. But that's exactly the kind of situation that convinces you that you're the only smart one because nobody else did it.

The world will not stop while he figures out how to deal with the colossal ramifications of his own actions. And that will cost him even more.
Here's a Youtube channel of someone restoring one of these remote Italian cabins to live in. It's not easy.

https://www.youtube.com/@MartijnDoolaard
Need to release your own changes if you distribute the application.

Whether you're able to statically/dynamically link the library without also having to release your own source.
If twitter is already dead, there will be no juice for these 2k employees to squeeze. Here's hoping twitter isn't dead yet.
First bullet point:

> Many will be asking for MoonRay integration into Blender, and the path to that is through Hydra. Blender support for Hydra is being worked on, and the MoonRay developers have indicated they are following this development and also see it as the way to go. The Blender Hydra implementation will need to mature, and renderer add-ons need to do additional work to integrate nicely besides what is offered by the Hydra API. So expect this to take some time.

Hydra, for rendering Pixar's Universal Sceen Description (USD). https://github.com/GPUOpen-LibrariesAndSDKs/BlenderUSDHydraA...
If you want to help your argument, especially since you're looking for an honest attempt at something, it's best to go by facts rather than memories. Another step that could strengthen your argument would be to define who is calling RMS anti-trans.

This is especially important, as time moves forward and people who never even met RMS read about this, to make sure we are relying on contemporary reports and not just fading memories.
(it's a fairly common trope on HN, any time there's a breathless clickbait-y title about some research results, there's a high chance it was tested only in mice, results for humans may vary, etc. etc.)
Imo its not cheaper (or has better quality) and is only worth it

i) if you want to toy around with it

ii) don't want to depend on the api to be available (or don't want to be censored or share sensitive information with a third party)

iii) finetune your own model that you need to deploy by yourself
I know someone with your conditions and they often start stories in the exact same way you did here, stories that might apply to like 80% of neurotypical people as well just like yours did. It just sounds a bit weird, and there’s no ascribing hidden meaning to someone’s words behind that.
The American College Crack-Up
Doesn't this auto-upgrade behavior punch straight through the reproducibility Nix is supposed to be giving you? It's not exactly a functional build system if the results you get depend on when you download the dependencies.

(I mean, I guess you could say that time is an input to the function, but that seems to miss the point.)
I appreciate the reply, but I think that's a bit oversimplified. Gmail, outlook, etc. doesn't have "topics" and the instance you join does matter to some degree, which is not the case for email.
There is often a criticism of Javascript, that new frameworks seem to appear every week. But it honestly feels like every week on HN there is a new Rust UI project showing up. Whether it is some new HTML/web thing, a native app thing, a TUI thing, etc.

Don't get me wrong, I think that is the sign of a very healthy ecosystem. I am just curious how the Rust evangelists will spin this. Somehow this constant churn on the Javascript side is worthy of snide, satire and ridicule.

IMO, UI development is deceptively hard. Rendering scalable graphics efficiently is hard enough. Creating a good layout engine and a set of reliable basic controls is even more difficult. But managing interfaces seems to scale quadratically with the number of controls, views, states, etc. I see programmers, over and over, underestimate how difficult of a task managing that complexity can be. This complexity leads to difficult to use libraries/framework/platforms. It also leads naive and ambitious developers to believe they can do better. This leads to more and more new libraries/frameworks/platforms.
Depending on the domain, this can be quite challenging, and the challenge isn't limited to FOSS. The non-business consumer market, particularly the desktop computer software market, is probably the most challenging when it comes to monetizing software. Even in the world of proprietary software, software companies still have to compete with pirated copies. This led to the introduction of activation, DRM, app stores, and subscriptions. Moreover, even without piracy, there's an abundance of free-as-in-beer software products that are either ad-funded or are subsidized by revenue from other parts of the business. I imagine that the people working on essential FOSS desktop projects like KDE, GNOME, GIMP, LibreOffice, Inkscape, etc. most likely don't make a full-time living working on these projects unless they're sponsored by a larger company like Red Hat or Google which makes its money from other projects. If I'm wrong, I'd love to hear counterexamples.

Of course, not all software is pre-packaged desktop and server software like Adobe Photoshop and Microsoft SQL Server. Making money from FOSS may be easier in B2B markets where companies tend to not sell prepackaged software solutions, but custom solutions that fit the customer's needs. Even with FOSS, just because the software can be downloaded and modified freely doesn't mean that the software is ready to use immediately. This may require modifying the code, which may be beyond what many business could handle. They could choose to hire their own in-house software engineers, but they could also choose to pay the software company, whose engineers should be more familiar with the code base. This is where I see more opportunities for making a living with FOSS, since not all software products are straight-out-of-the-box solutions.
I assume you're already doing this since you're on a microcontroller, but have you set

[profile.release]
codegen-units = 1
lto = true
A color is determined by 3 numbers, when those 3 numbers are chosen to be hue, saturation and brightness, that means that this color cannot be distinguished from a mixture of monochromatic light with a standard kind of white light (e.g. D65), both lights having certain radiant powers (per solid angle and/or per area).

In that case, the hue is the frequency or wavelength of the monochromatic light, the saturation is the ratio between the (weighted by the eye sensitivity curve) radiant powers of the monochromatic light and of the total light (so a completely saturated color is monochromatic, without any added white), while the brightness is the total radiant power (weighted by the eye sensitivity curve).

The red, green and blue pixel components of a display do not emit monochromatic light, unless the display is a laser projector. For any non-laser display the light emitted by a pixel component is equivalent with a mixture of a completely saturated color of the same hue with white light. This is especially obvious in the red of a sRGB display, which is much less saturated than a color that could be accepted as pure red. When two red colors have the same hue, the more saturated color is "redder", as it has less white and more red.

"Redder" is ambiguous as it can be also used when comparing colors of the same saturation and brightness but of different hues, e.g. when comparing two reddish oranges, where the redder has more red and less green, or when comparing two reddish purples, where the redder has more red and less blue. Any color display can show any color hue, the difference between the displayed color spaces is only in the maximum displayed saturation, which cannot exceed the saturation of the individual R, G and B pixel components.

When you specify RGB colors, you specify only relative values, i.e. by ratios vs. the RGB components of the brightest white light that the monitor has been configured to emit through its "brightness" setting. For instance, on a certain monitor setting the "brightness" to "75%" might mean that the brightest white has a luminance of 100 cd/m^2, while on another monitor model the same "75%" might correspond to a very different luminance of white, but in any case changing the setting will increase or decrease the brightness of all displayed colors, without changing their hues or saturations.

Both "#f0f0f0" and "#e0e0e0" are white and normally one would say that the former is brighter than the latter.

If on the axis of black to white one labels as "white" the brightest white and as "gray" the white of half brightness, then one may say that the former is "whiter" than the latter.

However this usage is not recommended, because it is ambiguous. It is much more common to say that a color is "whiter" with the intention to say that it is less saturated, i.e. it is a mixture of more white with less of a monochromatic color, than to use "white" as a synonym of "bright".
GPU is one part where modern design of Julia truly shines as it allows seamless reusability and composability. I wish the language gets the proper recognition and adoption
How were they able to generate / obtain the `apiKey` shown in the technical details in part 6?
I am willing to agree for one more reason. Success has many fathers and few have issues with sharing their story ( even if it is sanitized ). Few have 'intestinal fortitude' to go over their failings. Even if the game flopped ( I looked, I actually liked the aesthetics -- it struck a chord, so something was there ), we all can learn something from it and the author should be commended for it. It is not easy ( or fun ) to expose oneself to internet scrutiny.
GraphQL makes it straightforward to do conditional queries like:

… on Book {
title
author
if_viewer_can_purchase {
price
shipping
}
}

This is quite annoying to do with traditional REST without overfetching data you don’t need.
Emacs would like to have a word.
For anyone visiting Stockholm, make sure to visit the Vasa Museum. So cool
You can also consider the demonstrated qualifications/competency of the bidder. I could submit a low bid for a project and if I have no history of ever completing similar projects my bid can be rejected on that basis.

However (at least in the few governemnt bids I've been involved in) if the low bidder does not get the award, they can challenge the award and often do. Then the government has to defend their decision and give the reasons the low bid was disqualified.
<shame> The richest country is also the poorest.
I think you're conflating a number of different things that are distinct:

1) Copyright

2) Reverse engineering

3) Patents

4) DRM

5) EULA

Reverse engineering is legal. Copyright doesn't prohibit reverse engineering. But reverse engineering is also usually very difficult. There's no law that says you have to make it easy for someone to reverse engineer your product, nor should there be IMO.

The current patent system is crazy. Too many simple, overly broad patents granted by a patent office that doesn't even truly understand what they're looking at. I would definitely reform or abolish that system.

IMO the main problem today with anti-consumer products is not copyright but rather DRM. When the seller locks down the product and prevents the consumer from using the product as they please after they pay for the product and bring it home. DRM has a legitimate use to protect theft, but DRM has gone too far: it's not used just to prevent theft but also to control. The solution to this problem is not "free software" but rather protecting consumer legal rights.
The linked article is exactly what you’re describing. It’s linguistic code switching and covers Spanglish. It predates the more modern, broader use of the term, like having a work accent and home accent.
The Cajun accent of Louisiana sounds a lot to me like southern American English as spoken by a French speaker, which historically is its origin.
Yeah my view of wanting them to get OFF THE DRUGS is nihilistic. Not your view that enabling their horrible habit by making it easier for them with no therapy to correct it.

Are you high?
Theres also a Miami accent. People born and raised in Miami, fluent in english, yet have a particular kind of spanish accent.
AFAIK it has a bus factor of one, keep that in mind if you are going to build anything "serious" on top of it. I found it easier to configure than Keycloak, it lets you write short Python snippets for custom authorization logic, but it's about as heavy on resources as Keycloak. I hope he develops the project into a successful business, for users' sake if nothing else.
Not a Japanese company, but similar. I started my career working for a Korean conglomerate. Korean has similar honorifics as Japanese, as well an obsession for titles (even more so than Japan a I would say).

When I, as a Korean American, got promoted into a managerial role with direct reports, I tried to foster a more casual working environment and told my new minions they could call me by name. My manager chewed me out for that - my reports were to always refer to me as Team Leader John, not John (not my real name).

I quit that job, and got into my first Western (British) company. I ask how I should be addressing my managers and superiors, and the answer is “oh just call them by their first name, whether it’s your line manager or the CEO”. Culture shock.
That's not exactly a "big" failure. It looks like only YC invested, which makes it a <$1M failure.

Nothing like the ones listed, or Theranos or Juicero.
We actually have a long-standing issue regarding WebGPU[0]. Long story short, we want to support it, and Athas did some exploratory work a couple of years ago and decided that WebGPU wasn't mature enough yet. We already have a WebAssembly backend, so as soon as it is possible to access WebGPU from WebAssembly it should be relatively straightforward.

[0]: https://github.com/diku-dk/futhark/issues/1403
Not technically a startup, but you gotta include Arc in any YC-associated failure Valhalla.
I'm suggesting we know enough to rule out the spontaneous self assembly of nuclear bombs. And there's probably a few other things we can rule out by the same logic.
You don't have to manage your system with NixOS to reap the benefits of Nix. It solves very real problems that very much exist, it might not exist if you're a one-man show deploying WordPress to GoDaddy though.

Barrier to entry:

1. Run the nix installer

2. Enable flakes

3. cd project

4. nix run

This ensures you run the package with every dependency except the kernel pinned to a hashed version. If dependency hell is not a problem for you, be happy!
"I can't imagine that a deposition lasts more than a few hours..."

Heh. No. A good litigator will be prepared with enough questions to keep him testifying for most of the day on each case. No doubt there will be many objections along the way that will stretch that time out even more. There's zero chance that the boss's testimony (and Twitter's other corporate witnesses) will be consistent even in a single deposition, let alone 100s. Even the most craven arbitrator is going to have a hard time ignoring that, so the strategy will reap huge, literal, rewards. With costs and attorneys fees.
> THE FRUIT UNION Suisse is 111 years old. For most of its history, it has had as its symbol a red apple with a white cross—the Swiss national flag superimposed on one of its most common fruits. But the group, the oldest and largest fruit farmer’s organization in Switzerland, worries it might have to change its logo, because Apple, the tech giant, is trying to gain intellectual property rights over depictions of apples, the fruit.

What is Apple going to do next? Try to get a patent on rounded corners for rectangular electronic devices?
Just hire pentesters along with the development team. Make sure they are not affiliates. You can put in contract that as long as security issues are present they need to fix them before getting paid, which seems like a reasonable expectation. Even the best make mistakes, so let's at least leave those which are not trivial.

We don't trust building ethics, independent inspector comes and checks if everything is as it should be before it can be used by the public.
If it happens to you, you'll know what it's like.

That is what is like with all life situations. They are mystery until they happen to you. You don't know what cancer is like or the death of a loved one is like until those things happen to you, and you don't know what the boredom of abundance is like until you have it either.

On the latter, the important thing to get is that much more of what motivates us survival driven than most people realize. When survival is sort of guaranteed, a lot of motivation can dry up along with a lot of the juice of life.
DDoS in this case
So if we know Symbol.dispose in advance we can simplify the code? Why did they make it so unwieldy especially since it is a new functionality not requiring backwards compatibility hacks?
Agreed... Their SQL is awesome and seemingly only getting better.

My favorite is window aliases (I'm sure it's found in other SQL engines too). It's not only cleaner and less likely to accidentally introduce a discrepancy, but apparently also results in better performance.

> The three window functions will also share the data layout, which will improve performance.

https://duckdb.org/docs/sql/window_functions#window-clauses

I'm surprised some of the other big-name OLAPs don't provide this. *cough* Snowflake *cough*. Snowflake's query optimizer doesn't even seem to recognize common window definitions across multiple window functions.
Huh? Its double the headline of the article (24%).

Smaller numbers but higher percentage.
It's completely valid.

If capital wants to take on the risks of being suddenly fired and losing access to healthcare, injured on the job, sued for non-compete, being forced to relocate to keep benefits, lack the freedom of vacations, sick leave, parental and bereavement leave, being forced to commute to and work in an office with other people during a deadly global pandemic, deal with stress and potentially harassment and discrimination, sometimes be forced to surrender their work life balance to handle completely predictable emergencies, be forced to work on days off because of shortages and scheduling screw ups, be forced to travel to keep their job, they can roll up their sleeves and Get A Job.

It's ridiculous to pretend this isn't a valid negotiation.

If you own a lawnmower (capital), and you want to hire someone to mow your yard (labor), it's clearly and obviously a negotiation for appropriate wages. Why would it be ANY different if you're paying them to mow your neighbor's yard, and you pocket the profit???

Oh I forgot, you went to the HOA and pulled a regulatory capture coup d'etat and convinced them that only Certified lawn companies should be able to charge to mow in the subdivision, and there's a prohibitive fee and delays and inspections, making it practically impossible for the guy to save up and buy his own lawn mower to compete with you and "take on the risks" of business ownership you worried about.
This is true, but the smash cut is funny nonetheless.
> asio::ip::(tcp|udp)::address

You mean asio::ip::address presumably. That's not shared vocabulary. Suppose I'm writing a small program maybe a couple of dozen lines of code, and I need some IPv4 addresses. Should I bring in all of ASIO to have this type?

It makes plenty of sense for ASIO to live outside of the C++ standard library. But the standard library would benefit from these basic types as vocabulary.
> The biggest barrier to adoption unfortunately is not people's inability to explain what the tool is in my opinion.

That's simple: nix is a package manager and the language used by the package manager, NixOS is a Linux distro.

> It's that the tool is incredibly complicated, extremely hard to walk someone through compared to alternative projects, and honestly... In my opinion the problem it attempts to solve doesn't really exist.

From someone who is working as a DevOps Engineer for some years and managing Linux servers for a few years longer that thought is incredible naive. The problem of undefined and undocumented system state is a fundamental problem I encounter everywhere especially bad with legacy systems. I often do things on them blind and just pray for the best outcome, realising months later that some system was broken by one change I did and no one realised that for months.

> I'll take an "impure" os or package manager over a pure one any day if complexity is a thousand fold less and the learning curve doesn't require half a decade. Got stuff to do!

I thought the same first but unwedging Debian once a week on a different system is also not fun and a waste of time and having servers in some undefined state and no one who how the config is supposed to be and why or when it got changed, too.

The result in the end is that every system is different and unique and your Ansible playbook to run a common and good thought out task succeeds on 15 VMs and sometimes completely blows up the 16th because no one could have thought that the state of configuration there is so widely different.
I've had this experience myself, with RMS. I actually was asking if the FSF had the right to assert the copyleft on bison, and sign a document asserting that Bison's open licensing applied to bison - who had the right to assert the license, which was open, basically.

As a consultant for IBM. We were trying to USE bison, and this was when MS would chase every possible avenue to sue people for violation of copyright, so it was a big deal ... and had RMS been willing to assert that the copyleft applied to bison, that the FSF actually wrote the software and applied the copyleft to its code, IBM told me that it was willing to _defend the GPL in court_. For a signature, RMS would have had the 800-pound gorilla defending the GPL. (We were also going to make a donation to the FSF to help them along, although that wasn't part of "the deal" - it was, like, "hey, you do good stuff, we're planning on putting this in the project budget next because if we can use your stuff, that helps us a lot."

And RMS first off refused to say the copyleft was assigned to bison; it did, of course, everyone knew it, but we needed the legal affirmation or it was pointless. (I can claim that I can fly, everyone knows it, but unless I'm actually airborne at some point...) Then he asked for money (less than we'd talked about budgeting internally) ANYWAY, before we'd even brought it up, if memory serves. (It's been a long time.)

Just... a giant moment of jackassery.
FPGA but via a network? Sounds a little bit like an oxymoron.
Ah ok, it's fine for you to call everyone too stupid to understand anything outside of their field. However, when I challenge this idiocy, I'm the one belittling people. Interesting take.

Your mindset is how we ended up with the lie that COVID came from bats and ended up vaccinating children with a dangerous untested vaccine. Never question thou holiest of holy "experts".
Amplifier tubes have only a little overlap, if any, with the tubes you will find in a typical AM radio like the one described. Maybe the rectifier or the output tube.

There is still (!) plenty of old stock of radio and television tubes out there, however.
“Imaginary problems are the roots of negative developments”
That’s a great point, never thought of it that way. Hierarchies always exist, if everyone’s aligned you need not formalize it (very rare), else formalizing it helps.
Lucid Air EV