skysight-inc/HackerNews huggingface dataset:
I’m not familiar with C#, so I probably should not have included it. But Kotlin, Scala 3 (with a compiler flag) and even Java with static analysis should be sound, if I’m not mistaken.
> Sandy Bridge is a P4 derivative with all the faults fixed and the sharp edges filed off, not a P6/core 2 derivative.

That SB reintroduced netburst features doesn't change the history of the µarch. That's like saying Netburst not using a ROB means it was an evolution of Alpha rather than P6.

SB was not a renaissance of Netburst, it was a reintroduction, into the Core family, of features which Intel had first introduced in Netburst. Something which had already happened previously (e.g. hyperthreading in Nehalem) and would continue in the future (e. reintroduction of non-unified schedulers).

The "faults and sharp edges" of netburst were all caused by features which were at the core of netburst's identity, that's why it was a dead end and intel had to reset back to a sane working slate. As the article notes:

> Some of the fundamental ideas behind the architecture were definitely flawed.

And that Core was able to successfully integrate over time features first attempted in Netburst is exactly what you'd expect: many (though not all) of the individual features were not intrinsically bad and in fact several had been deployed successfully by other companies.

As the article specifically notes, the issues were introducing them all at once:

> Netburst debuted a mountain of new microarchitecture techniques. Some of these had been implemented by other companies, but were new to Intel. In general, the more you depart off the known path, the more risk you take. More changes mean more moving parts to tune and validate. Intel clearly took on way too much risk.

Especially in an architecture whose fundamental concepts and tradeoffs turned out to be unsound.
I feel like this is the end result of giving away hard work for free when it should have been charge for all along. When you give your work no value, people will perceive no value in your work.
Because you really want a Python API?
I think the wrong message is getting made.

The takeaway I am getting is: don’t interact or communicate with open source projects you use.
I don’t know much about the European job market, but you can see lots of examples of US job positions and their salaries at websites such as https://www.levels.fyi.
From The Phoenix Project: https://allengeer.com/how-to-handle-brent-in-the-phoenix-pro...
My understanding is that CH4 breakdown in the atmosphere isn’t a matter of exponential decay either but is (or could become) rate limited by OH radical availability. Such that the half life increases as more is in the atmosphere and it’s possible to totally outpace the breakdown even at constant emissions.

https://en.m.wikipedia.org/wiki/Atmospheric_methane
> When my company now pays money for it, my expectation definitely changes.

Familiarize yourself with the difference between "free beer" and "free speech".

The F in FOSS refers to the latter, you're fixating on the former.

The FSF has never objected to charging money for Free/GPL software. Programmers need to eat too.
Because most startups aren’t going to grow in the long term to profitable businesses. Either they are going to flame out completely or they are going to get acquired, the product discontinued and the founder is going to walk away with money and post an article on their blog about “our amazing journey”.

As an employee, it’s in your own self interest to do resume driven development. Your “equity” probably won’t be worth anything so you might as well work toward preparing for your next job.

As a founder, you can’t offer the compensation of a larger company. What you can offer is the chance to work on “cool cutting edge technology”.

At this point in my career, I’m more motivated by being able to describe successful outcomes than cool new technology. But I do understand the motivations. I’m also not an old curmudgeon though that considers the cloud is just a bunch of VMs.
Sell it all on eBay and donate the money to a worthy cause.

Turning hardware into value is the hard work that will benefit others.

Good luck.
I’m not sure what you mean by this example. From what I see, somebody submitted a bug fix that hadn’t been approved/merged by you for 6 months. Then some quite rude conversation happened “Don’t act as my free time is owned by you”. I mean both sides look quite ugly in this particular case to be honest.
You certainly seem to be asserting something. Whatever any evidence indicates is only probabilistic and thus needs to be hedged with modifiers to be taken seriously.

And regardless, your words, and everyone else's, were still determined at the beginning of time, if your argument is true.

That's why this line of reasoning is self-defeating, since if one accepts it they will ignore you since they literally can have no effect on you, nor you on them.
As someone with over a decade of professional C++ experience, here are some things your company might experience during this migration:

- A dramatic reduction in runtime crashes, and a ~70% reduction in security vulnerabilities (based on Microsoft's analysis of security bugs, but also personal fuzz-testing experience).

- Much better out-of-the-box tooling. You can set up cargo, VS Code and rust-analyzer in 5 minutes. "Maintaining the build system" will typically become a thing of the past. Rust also provides many verification features for free that would require setting up static analyzers for C++.

- A much easier time integrating third-party libraries. But you may loose access to certain domain-specific libraries, depending on your problem domain.

- Safer use of complex threading and/or async, if you need them for performance. Look at the Mozilla experience converting complex concurrent C++ modules to Rust. They've written a lot about it and it has almost always been a giant win.

- Hiring is a tradeoff: Depending on where your company is located, you may have more local C++ programmers. But if you do remote hiring, the Rust talent pool can be fantastic.

- It's easier to train people from scratch. Rust is not a small language, but it's a lot smaller than knowing the entire history of C++ gotchas and idioms. Also, Rust provides much better guardrails for novice Rust developers. It's feasible to take a strong junior developer, train 'em up, and turn 'em loose.

A migration like the one you describe makes the most sense if 3 things are true:

1. Your C++ codebase is small enough to incrementally rewrite (and your team knows how to manage an incremental rewrite without too much loss of velocity).

2. Your problem domain does not rely on major C++ libraries with no Rust equivalents.

3. Your developers are enthusiastic about Rust.

If any of those three factors were missing, however, then I would normally advise against a rewrite.
Use the example in the article. You basically write a letter to your fellow employees saying (I’ll paraphrase) “im outta here because the talents and ideas that made this place successful are gone”.

Can you do that in Europe and face no consequences?
This reminds me of Reddit's approach to mobile. They make their mobile web interface excruciating to use, and block features client side just to push you onto their app.

I'm guessing it has to do with mobile users being more lucrative?
On the font pages, they use this as the example sentence:

> The quick brown bunny jumps over the lazy dog.

While the site is trying to be quirky and cute, replacing 'fox' with 'bunny' doesn't showcase what 'f' and 'x' look like.
I have the old flag from my bike trailer we used when the kids were small that I mount sideways on the rear rack, sticking towards traffic. It hangs out about a foot past me and encourages traffic to give me some space.
Why wouldn't I just self-host the fonts on my server?
What are the benefits of such CDN? Years ago I could understand it because it may reduce latency (cache), but since browsers don't cache from 3rd party servers anymore, also this is argument is obsolet.
Straw man. Cows should be grazing, not being locked up and fed corn.

Grazing cows actually make the environment better.

So rather than blaming cows, blame the way they have been grown over the past 50 years or so.
Not a fan of range extenders; definitely a fan of (carefully-selected) fixed-frequencies, distinct SSIDs on unique APs, and per-MAC rate limiting. Use wired Ethernet wherever possible. Choose the physical placement of your APs wisely.

As for mesh networking, nice to have in the suburbs, though never as good as a fully-managed, wired-AP solution, especially in Manhattan high-rises.
The author followed up by stating:

> As time went on the wording of the +1s got stronger, people demanded that it be implemented and expected it to be scheduled into future milestones.

I don't think they thought the +1 was an issue with respect to prioritization. Rather, it is an issue because it is a form of confirmation for users to behave in entitled ways.
I don’t install social media apps like Reddit, Facebook or Twitter. And all of them are trying to force me to install their apps. There is even a similar restriction with Facebook messenger, which you can use in mobile Chrome if you use the “request desktop site” feature, but not on the normal mobile site.
Build infinite list in Svelte with ease
You’re missing the fact that employees who are interested in their own career would be less interested in a Rails stack on their resume.
Grab launches GrabMaps as a new enterprise service
> Shortly after I moved much of my funds into crypto, and would do it again for the security from arbitrary seizure.

I don't think they would've been able to seize the money. But in any case your approach doesn't work, you still owe that money. Automatic renewals is a scummy practice but if they do have a legal claim you won't get out of it by being hard to find and keeping your money in crypto.

Probably best to treat it as an expensive lesson and remember to close your subscriptions in the future.
Yes, the processes of incentives driving outcomes is economics.
The random number that you're trying to find by means of (yes, repeatedly) hashing, is dependent on the transactions in your block (which are hashed together in a Merkle tree).

Not only that, but the number you're trying to hash is also dependent on the previous block (hence it being called a blockchain).

So as soon as another miner mines a block, the block you're mining immediately becomes invalid. For two reasons, the block height of your block is now too low (it has the wrong parent) and it (most likely) includes already mined transactions.

So even if you happened to still mine your current block, it will be rejected by the nodes in the network for having the wrong block height and for including already mined transactions.

So, you have to assemble a new block, which uses the latest mined block as parent and you have to include new transactions from the mempool.

There's a cost to doing this, it takes time away from the actual hashing, which is what I meant with "starting from scratch".

For the reasons outlined above, you're not mining blocks independently from everyone else.
Exactly. A "perfect" fix next week is not better than "drive it gently and bring it back on Monday so I can look at it properly".
Yes society has made a lot of progress - in offering more freedom, luxury and opportunity to more people than ever before - like eating meat.

Give me an example of the reverse happening. We cannot "choose" our way out of this situation by somehow getting the entire globe to agree to want less.
If you’re interested in something that creates a great developer experience on top of container runtimes but which supports more complex workflows and apps than docker swarm, check out withcoherence.com (I’m a cofounder). We orchestrate containers from dev to prod in your own cloud, without abstracting away what’s happening under the hood, but also without forcing you to deal with all the operational complexity of “doing it right”
I would have to read it to see what you mean. I cannot imagine a world in which the normal way of doing immediate mode graphics was more efficient than retained mode.
Wait, serious question, is a wave in water or on a string in some way also understood as a particle?

And, even from the perspective of field theory, aren't fields defined by the type of waves moving through them?
egoid333 wrote:
> what kind of ai and crypto projects do you work on? just curious.
>
> i have a similar story.

Hello egoid333: You are dead, so few will see your comments, including the poster, as his karma is too low. But as you clearly respond to:

> Are there other misguided people like me?

I tried to establish a contact, <deleted>

--

Regardless, good initiative! I hope you'll get your life back on track. Or maybe consider tech isn't your best bet to do so, a-t a-l-l, as it requires some isolation.

I've experienced someone schizophrenic in my life, and I must confess that wasn't the best of experiences, as it was intensely demanding, in fact impossibly so because of past events. Still I have respect for the intensity.

I agree the medical establishment can only do so much, and that the inclination there is to make you pay handsomely for something that can't truthfully be called a treatment. That's putting it mildly, as there are perverse financial incentives at play, not something you want to have to deal with. It's complicated.

That is, IF you can afford it to begin with (not likely), which is the point some evidently fortunate posters seem to miss. Duh. Must be disheartening to read.
I'd say it was more like committing secrets Into an early alpha repo... understandable at that stage of the project, likely never to be repeated.
Pfft, I thought this was a forum for hackers.
Sites shouldn’t even load google analytics without consent. Almost no website blocks GA before you give consent.
Rust and Go are different classes of language, where Rust is a non-GC memory-safe language, and Go is a statically typed GC language.

In Go's language class of statically typed GC languages, Go is much worse than the best languages, which are Kotlin and C# (Go lets you forget to write error handling, had no generics until recently, uses duck typed interfaces (!)).

In general, Go's inferiority can be traced to its root cause, which is the Google Go designers having severe Dunning-Kruger syndrome because they think they are good because they invented C/Unix and work at Google and don't realize they have no clue about programming languages in general and were only successful because the limited hardware at the time didn't allow sophisticated programming languages and thus allowed a terrible language like C to succeed.

As a language class, non-GC memory safe languages are far better than statically typed GC languages since they don't have the overhead of a GC and can guarantee the correctness of concurrent programs since they are data-race free (in Go-like language two threads can share the same data with no checks whatsoever resulting in arbitrary racy behavior), can make other guarantees enabled by the linear type system and use composition instead of implementation inheritance.

So in general you should always use Rust unless existing framework or libraries for other languages make solving the problem much easier and the app code is small enough that the extra problems in using a subpar language aren't too bad (e.g. you probably want to use bash for system administration, Python for simple deep learning projects, Kotlin for simple Android apps, Swift for simple iOS apps, TypeScript for simple web frontends, etc.).

However, if you plan to write a lot of code, then just using the best language, i.e. Rust, is probably better since the time to write or correct dependencies will be small compared to the sheer amount of code you are planning to write for the main software.

If you are willing to give up good performance and a large library ecosystem for correctness, then dependently typed languages like Idris are also an option.
Maybe I could get it done in the same time, but I'd be really annoyed, and less certain what things are intended for. An IDE can really carry the burden figuring out what things are, but you're going to lack some context.

Usually it doesn't matter WHAT things are, I need to know WHY you have a variable, and what it's intended use is. That can be explained in the variable name a lot of the time.

I have the same argument against the no-comments evangelists, and wanting to squash all commits into one when they're merging. Yes you can read the code diff, but that only tells you what, not why, something was changed. Why did the API endpoint change? Why do we have to call the payment processor before this event rather than after all of a sudden? Why did the add to cart button move up one div? All very useful information when you have to come back to fix things.

For the no-comments evangelists, I understand the idea is to make the code as self-documenting as possible, and that's awesome, but you can still miss out on the why, and sometimes the Why is entrenched in external business requirements that aren't in the code.
You're missing the point: auto-switching between APs might be an anti-pattern, especially in scenarios where one has WiFi Direct-based devices, or an iPad dedicated to device control. Blame Apple all you want, but that behavior is what professional integrators want.
How can you tell what has impact, though? What's the point in paying for school lunches for kids who have no interest in learning?
Sqlassert – Go package with assertion helpers for SQL databases
The behavior we see due to the private ownership of media and news publishers betrays the colossal failure it is for the public and nations at large to have our society's self-reporting undermined by profit motives. News and media need to be treated as protected speech, with more formalization and more regulation. Leaving the governance of our society's self reporting to greedy Capitalists is a clear and active recipe for doublespeak and fascism.
Eating meat is human nature (and biology). We can digest just about any meat there is. We cannot digest any plant. Try eating a tree branch and see how far you get.

Likewise humans (like other animals) will always have tribal and territorial tendencies manifested in enslavement, war and conquest. First-world nations developed over centuries and still have countless problems, and they're only a minority of the global population. The current reality is far worse for billions of people around the world from rural China to Africa to North Korea.

Do you really think this all continues because it's just a story? If these situations are so easily changed then please go ahead and do so.
You need to understand the fact that many are willing to own bare land and put it to its less than theoretically optimal usage. In fact they will fight against attempts to develop it.

It's called land banking if you haven't heard of it before.

I'm not sure how any of your comment follows.
Google Fonts: "1424 of 1424 families"

Bunny Fonts: "1429 families"

Presumably Bunny Fonts is, essentially, just a pass through to Google Fonts.
This exactly! I am a solo maintainer on a very small Android app. I find it very useful when users vote for issues with the :thumbsup: emoji. Otherwise I have no real way of knowing which new features are popular with the community.

Comments that add nothing to the issue but just create noise in the notification feed are annoying.
Could you power a house with a few dozen of these RTGs?

Or are they just so obscenely expensive?

If you could use these then you wouldn't really need batteries, which you do need if you go solar.

Is it even possible for a mortal to buy a RTG?
macOS only, written in Swift. so pretty useless to everyone else
She was the most junior employee, and yet she worked 6 years in a call center. Yeah, that's extremely believable. Oh, and the colleague that went to a concert... that was just a pure indignation pump.

I always wondered how many of these kind of reddit posts are real. This one is just over the top, but I'm betting there are quite a few that play things just a bit more conservatively and pull it off.
You are being deliberately obtuse. There are people who are enslaved in societies where slavery is illegal and, as a whole, considered evil by a very large majority of the population. People are sometimes kept in bondage by force and that force does not come from the government or by the society at large or by that societies views or consent. Of course, all of this is obvious and thus you are clearly trolling. If not, then you are a sad example.
Ok, right. But then it should still say either "booleans are just numbers" or "numbers can be interpreted as booleans, i.e. are truthy or falsy".
> in a static ruling system what you see is what you get, where as in a dynamic typing system what you see could be anything at runtime.

What you see in a statically typed language: IBlaha blah. What could blah be? An IBlaha. What could IBlaha be? Anything! The type has not gained you anything.

> The only citation I have is the tenuous grip I have on my own sanity

That's an argument from authority where you are the authority. It doesn't work on HN since we are all skilled developers. I've also been a software developer for decades and I can count on one hand the times static types has provided a tangible benefits.
I've tried some game development in Rust (but not a professional game dev), and its really not a great language for it I think. The strengths of Rust of knowing that its correct are not great for games, which is basically just rapidly changing and refactoring constantly. I could see doing base level libraries in Rust, so you know they are memory safe, but I wouldn't want to develop a full game in it, even though games otherwise fit most of the other requirements rust does well.
> However I now see that my use of the tool provided no value to the company, and I was not a paying customer of any of their services, so why should they provide me with free support.

That is not true. If the use of the tool provides "no value" to the company, then why on earth are they making the tool available. Yes, there is no money exchanging hands, but there is definitely some value.

Here's some value a company gets when someone uses a tool/piece of software without paying money (source: my company has a full feature free tool that competes with our paid offering, and often wins).

* awareness of the solution in the marketplace

* developer attention (way way easier to get a developer to try a free tool vs one that costs $0.01)

* bug finding (often in environments that would be hard to stand up for the company)

* user testing (related to bug finding, but often users will give feedback about feature direction)

* market share (if they are picking your free tool, they aren't paying for a competitor)

At my current job, we often leverage this (our GitHub issues repo and forum are main sources of our roadmap).

That's not to say that you should expect the same kind of service when you are a free user as when you are paying money. But attention is valuable too, esp of developers.

And it's not like if you pay money, a product company jumps to build whatever you ask for. Unless you pay a large amount compared to their current revenue and even then, if what you want conflicts with their long term vision, wise leaders won't.
Which ones aren’t honest?
Possession is 9/10 of the law. What some tax board thinks only matters insofar as they are able to enforce their will. People think governments are omnipotent. They are not.
The impact is they aren’t malnourished? Seems like a good goal.

Edit: we prioritize feeding people over giving them educational science articles; seems appropriate
I see some differences. The python one can enumerate all cars in the account, the node.js one doesn't have that....you have to specify a VIN. Python one has figured out how to enable specific seat heaters at start, node.js one says "Not sure?", etc.