skysight-inc/HackerNews huggingface dataset:
Apple Silicon:

Be node ahead of competition.

Solder memory on-package.

?????

Profit!

Not that Apple Silicon isn't impressive but I think we ignore the shortcomings and take a lot of what other processors do for granted.

Silicon often struggles on workloads that don't use some sort of hardware acceleration. If you never go off the beaten path it is very compelling.
That's completely consistent with the GP's point that companies who are struggling or companies that are taking big decisions tend to hire McKinsey to do some reports for them. That applies equally to some really successful clients whose successes McKinsey deserves essentially no credit for.

The company that actually advised Enron on how to do its false accounts, Arthur Andersen, was broken up. McKinsey's documented involvement was fluffy stuff on management culture and writing press releases citing Enron as a success story which look pretty funny in hindsight.
This is because FP64 is emulated on the NVIDIA Ampere as it is missing dedicated FP64 hardware. This is not a fair comparison.

FP32 is 64x faster on NVIDIA Ampere than FP64 per: https://www.nvidia.com/content/PDF/nvidia-ampere-ga-102-gpu-...

Ampere has 60 TFLOPs of Performance on its top GPU, the Hopper per: https://en.wikipedia.org/wiki/Ampere_(microarchitecture). Which is roughly 50% to 100% faster than Rocket Lake depending and that doesn't account for the parallelism/memory benefits that comes with the GPU architecture.
You sound much more a freelance developer or a single person development agency than a software consultant, I guess we simply describe those roles differently and don't assume the same thing when talking about "software consultancy".

The thing you are describing sounds like the first phase of a project where you are gathering the requirements, in a one-to-one business relationship with a single customer. "Sell before you build" as far as I understand is usually used in a one-to-many scenario, where you start selling (or better, marketing) a product before building it.
Downloading torrent is fine though. You can connect to peers just fine, it's just the other peers can't initiate connection to you which is bad for seeding.
Which features do you need that docker compose can't meet?
I'm not terribly familiar with Go, but surely the comparison here must be with Rusts Reference[0]? It is a bit shorter than the Rust Book (a simple print-to-pdf says 435 pages vs. 664 pages, and 104 pages for the Go spec).

0: https://doc.rust-lang.org/reference
I think you have the right idea already, so it just depends on what you want. I believe that learning Rust has made me a better programmer because I am now explicitly thinking about ownership rules and references no matter what language I'm using. Types and memory allocation are also more explicit in Rust than in Go, adding to learning aspect. I don't think learning Go has made me a better programmer. It was just another pretty standard language. But I already knew a range of other compiled languages previously and Go wasn't sufficiently different.

Like you said, for "getting things done" that is not low-level, systems, or game programming, Go is the more reasonable choice. It's more straightforward, faster to iterate in, usually more concise, has easy concurrency primitives, and is more widely adopted in the industry.

TLDR; I'd go for Rust if you want to optimize for learning and Go otherwise.
> I'll make these four lines of code a function in case I need to call it more than once later on - you know, what if that's needed?

The code example is not always right.

Beware, if you know it will be needed, you might as well make it a function now. Likewise if you think probably it will be needed, why not make it a function now?

It’s not a good review comment or rejection to say “yeah but I don’t want to do that because it’s not yet needed”. Sure, but what if you are just being lazy and you don’t appreciate what it should look like long term?

The “I don’t want to write a function yet not needed” is not a clear cut example.
Go has also wasm output.
Douyin, a completely different app ran by ByteDance is popular in China. TikTok is not.
Go can also compile to WASM.
This solution is too simple, elegant and doesn't result in much publicity and money flowing into the pockets of politicians. I hereby demand that we classify these as heavy quadricycles that require a motorcycle license that is incompatible with car drivers licenses and also requires an additional trailer exam if you want to carry more than 15kg of cargo.
Uber is best understood as a legal entrepreneur.

Their skill lies entirely in breaking laws in a way that allows them to make more money than the fines they pay.

In addition to their legal entrepreneurism their next skill lies in hiding externalities. They push costs to everyone else (drivers, riders, cities by massively increasing traffic, everyone who lives in those cities who have to deal with the noise and pollution of the additional traffic, etc) without having to bear any of it themselves.
> achieves 87% of the performance of the Intel 12900K and Nvidia RTX 3090 combined

This sounds insane (not in a good way). A 3090 destroys M1 Ultra in tasks like machine learning, 3090 being 5x-10x faster than the M1 Ultra.
I write JS 99.9% of the time.

I would definitely pick Rust as it is more different than JS.

Yes, there is a higher learning curve. But it will broaden your perception on programming languages.

As an added bonus, rust is very popular to create WASM stuff. So you can apply it to the JS world.

Happy 4th
Learn both. Go takes about 10minutes to write code in, a week to figure out harder stuff. Rust takes a few weeks. Both are good to know and fun to learn
Funny how a lot of these failing crypto companies are piling up in Singapore. MAS might have zine explaining to do.
I wish Ghost supported Bitcoin and Monero, without a third party processor. Even Jack Dorsey has advertised it suggesting it could be decentralized with this single feature. I hope they get around to implementing this.
I personally enjoy Rust more than Go, but if you’re considering the career angle then Go has a huge advantage of more jobs.

Rust has a steep learning curve, like you said, which is one reason why it won’t be nearly as common as Go in the workplace.
In researching a few home improvement topics, I was amazed how often I found the exact same articles being posted in multiple places with different authorship asserted. It made me think that if I ever wrote anything original it would have the same end. Not to say that this technique prevents this or not, but I can understand the perception of the threat.
Wow, that sounds like quite the variety of fun when you were younger; kudos! My dad was very much into sports, so my siblings and i - as you can imagine - played lots of sports in our youth; somewhat on teams but more so just with each other. And honestly, as fun as team sports were, i enjoyed my time tons more with just our little family unit when i was a kid. Kudos again to you for your fun youth! :-)
> We need to stop saying don’t roll your own crypto and start teaching it with good examples and good explanations.

Or teaching it by silently noting and exploiting the flaw, rather than put out a public blog post.

Once people know you are elite, all such things do is draw attention to yourself.

We live in terrible times, it's not a good idea to engage in cyber dick waving that only serves to draw attention to oneself.
I disagree.

There are a lot of valid reasons why a start-up might prefer Kubernetes to other solutions.

A simple and good enough reason is the need for variable compute:

You might need more computing sporadically (say for example you're doing software in the sports industry; your demand changes with the number and size of events, as well as on weekends).

Another reason might be a start up that allows their customers to execute some type of arbitrary code (eg a no-code product). This can vary from customer to customer, and it can also vary within the customers use cases.

Imagine having to manage all these storage, networking and compute resources manually... Or going full circle and managing it with a bunch of puppet/ansible/shell scripts. Now you slap some automated scale triggers on top that fires off these scripts.

Congratulations! We've built something that looks like Kubernetes; if we squint. There's some smoke coming out of it. Documentation? Lol, we don't have time for that. we are a company that gets shit done, we don't toy around with Shcubernetes and documentation! Error handling/monitoring/reporting? Eh, just read the code if something fails. Need to add cert issuance? Yeah let's implement our own ACME integration. Network ingress? Let's just have a 500line haproxy infront of an 2000line nginx config; no big deal. DNS? just append to named; who cares?

The name for the "we get shit done" crowd should probably be "we don't give a shit about anything and have others solve problems we created because of our lack of thinking and foresight", but it doesn't sound quite as memorable.

It's just people who are comfortable cutting corners at other people's expenses. When they have to own the shit they made, they start blaming others and leave the company.

Sorry for the rant.
Canadian here. I have been using Robertsons for forty years. It's all you can get at the hardware store: #10/black-handle screwdriver, #8/red, #6/green and #4/yellow. They are a joy to work with. They're so good nobody will buy the old straight slot or Philips.

Slide a screw onto the screwdriver. Hold it horizontally. Holds fast. Can you do that with Torx?
"I think the most appropriate advice is to choose a stack which the founding team is most familiar with."
I'd think that's exactly what typically happens most of the time. But the degree of stack-lockin that occurs with startups still surprises me even when it's clear a better choice might have been made. Mostly due to management not being prepared to grant the necessary rewrite time.
> where free and fair elections, along with human rights, are being turned down this year

This is precisely the sort of hyperbole OP is describing.
This is the first I’ve heard a recommendation to learn elixir. I’m definitely interested based on your description + a quick google. Is there anything that comes to mind in terms of what it does different from Go/Rust that makes you recommend it? My understanding was that I’d get these types of benefits from those two languages
If you really want to understand how programming languages work internally, you should look at assembly language or possibly at the bytecode interpreters of some scripting languages.

C is still fairly high-level.
>But I can't imagine it would be allowed to even have this as an operating procedure this when it puts the plane in a situation where it can't be certified?

Anything can be allowed with enough omission, lawyers, scapegoating, campaign donations, and enough tolerance for blood on one's hands. It's called regulatory capture and it's the fundamental conflict-of-interest between most engineering orgs and their in house Quality programs, with the exacerbating effect that if you can coerce the external regulatory forces to give you a pass, there's really nothing your Quality people can do but resign in a gesture of "I won't build that".

You will never see the regulatory apparatus work as designed if it isn't willing to just say "No" to that which clearly violates prescriptive certification criteria.
> Apple utterly dominates the mobile phone CPU landscape,

That seems to be an interesting definition of "dominates". 14% of global smartphones from independents. 24% by Apple's claims. A curious kind of domination.
The advantage of rust is that it protects you from common errors in c.
if i had to choose between c and rust as someone who likes go, i always would choose rust.
The truth is at scale the last thing you want is a nest of unmanaged complexity, so it’s also the wrong instinct there. It’s usually contact with the real world that dictates what needs the extra engineering effort, and trying to do it ahead of time just means you’ll sink time up front and in maintenance on things that didn’t turn out to be your problem.
Is there somewhere I can go to understand why McKinsey has almost cult-like status among large corporates?

Some of the stupidest decisions I've ever witnessed has been driven by multi-million dollar strategies from McKinsey. At a place I worked previously McKinsey advised in-housing software development to spark innovation and digital transformation. Then three years later in 2020 to it was advised that software development be outsourced to cut costs.

Obviously this was a move of utter insanity but for our executives it didn't matter. If McKinsey suggested it, we did it. There was literally no debate on these decisions no matter how hard we tried or how obvious of a mistake it was.

During my time at said company I was working on an innovation project which imo would have been fairly revolutionary for the company's future. For about a year we gathered input across the business and it was understood by every team we spoke to that this technology would be central to the continued success of the company. Importantly, it was understood the importance of us owning the IP and being market leaders in this technology so we could use it as leverage.

The cost of the project was estimated at around £100,000 - which was a fraction of what we were being billed by McKinsey every year. Encouraged by the the overwhelming support we got from every segment of the business and the relatively affordable development costs, we pitched our plan to the executive team.

A couple of weeks later we learnt that the executives deemed the project too expensive and sent us several companies who were suppliers of McKinsey who had built similar solutions. We tried to explain to executive team that the tech we wanted to build didn't yet exist and these solutions from McKinsey's suppliers were no where near ready for rollout, and in most cases these suppliers were actively lying about their tech. But it was an impossible battle. In their eyes we knew nothing despite months of research and McKinsey's word may as well have been gospel.

I left the company shortly after this and have heard things have continued to go down hill. I guess I never understood why the executive team seemed to just defer all of their executive decision making to McKinsey in the first place, especially given the lack of success and costs. Why was our own executive team not better placed to form corporate strategy? Is it common for corporate executive teams to just serve as puppets to large consultancy firms like McKinsey?

The relationship said company had with McKinsey was unlike any I've ever seen before. In my experience suppliers are normally on the backfoot, not calling the shots, yet this doesn't seem to be the case for McKinsey. It seems many corporates are more than willing to follow McKinsey over a cliff and I have no idea why.
> good and easier way to deploying 10-15 services

Why are so many micro-services needed? Could the software be deployed in a more concise manner?

Not getting into the whole monolith-vs-services arguments. In both cases, complexity of deployment is part of the cost of each option.
??? I thought that was what it was for. Or maybe for making wacky collision vids on YouTube?

Tesla just closed their whole self-driving office in San Mateo, and fired ("for poor performance") most of the staff, directing some to come to work across the bay. For now.

People still employed on that activity would best update their résumés. People who paid for self-driving already? I would ask for a refund, in your shoes. (I wonder if they will comply.) People fired for cause without due process? Sue. Really. How scummy is it to do a mass layoff, and make toxic shit up just to avoid complying with laws for mass layoffs?

Supposedly the "important" people are still employed. For now.
Do you know when I can find potential buyers?
I appreciate your style of acknowledging the points you agree on even as you dispute other statements. In this spirit:

>> Economically, switching to non-polluting energy is a shoo-in.

> I agree.

I also agree, but I have some questions about your position re nuclear.

Solar panel lifetime is approx ~20 years. Is the e-waste from solar panels a pollutant? If not, is the spent fuel from a nuclear reactor a pollutant? If so, how do you reconcile the apparently inconsistent position that solar is non-polluting but nuclear is not?
Like you said, most of these clinics have 2 assistants who do pretty much everything (accepting calls, submitting prescriptions, etc.) Sometimes, the doctor will also bring in an aspiring resident (mostly international medical graduates who cannot find clinical experience in the US easily due to their visa status/restrictions) as a volunteer or a paid-under-the-table-for-$12-per-hour to do some miscellaneous stuff around the clinic. But that volunteer's hours are sometimes on a need-base planning (meaning, the doctor will call the volunteer a day or two before if the clinic needs extra help).

Malpractice insurance for internal medicine (general medicine that I'm referring to) is ~$33K-$34K in NY area based on the link you've provided.

Now let's do the math to readjust my estimates.

One full time staff with $30/hr * 2080 hours in a year = $62400 => let's just double that to cover everything like their health insurance and liability insurance so each full time staff costs = $125000/year

2 staff * $125000 = $250000
Rent = $60000 (the doctors sometimes own the practice, but let's just assume it's a rental)
Malpractice = $35000
EMR system like eClinicalWorks = $10000 (amortized for upfront and yearly costs; software like eClinicalWorks costs ~$600/month on average)

The total expense of running a primary care (internal medicine) clinic = $250000 + $60000 + $35000 + $10000 = $360000 (let's just say $400K/year)

When I said these clinics on average make $1MM/year (of course, they are all near NYC/NJ metro areas), I truly am underestimating the income these doctors get from each patient visit. As an example, if I visit my physician at NYU Langone for my yearly check-up (at most a 10-mins encounter), the net reimbursement from my insurance they get for my visit (after the insurance company's discount/rate negotiation) is ~$250 without including the lab fees. Out of emergency and convenience, I happened to visit one of these primary care clinic doctors where my wife used to work at, and the doctor charged me $80 (that was back in 2019) in cash for an ear infection check (total of 5-minute encounter) and that's because I paid in cash and because my wife used to work for her. All of these doctors that my wife volunteered at or worked for (she got paid $15/hr max from some of these docs) are making a load of money from these clinics because we know a couple of them personally as well.

Again, I'm not saying you are understating the profit margins. You probably have been working with the clinics in some economically depressed or low-cost-of-living areas. I am only sharing what I know for truth in terms of the income of these primary care clinics in NY/NJ area.
> plus he can control his income relative to impacts to benefits

In other words, benefits abuse?
Hi! I know I haven't supported my claims in the readme. But if you see the syntax for beast build files, you will see that indeed syntax in beast is much simpler and intuitive. For example, you have strings and integers for variables. You can dereference them easily and even create new variables of any type from other variables. You can declare variables inside a build rule. All in all, the syntax is inspired from python, since everyone loves it so much.
This is not all, I'm currently benchmarking Beast. The new release: Nimble is turning out to be way faster than Make and even matching/overtaking Ninja (currently one of the the fastest build systems in the community)
But you are right in saying that I should include this in the readme. I will surely post this after the benchmarks
Any type of behavior that tells customers to go somewhere else will lead to a net negative outcome. Halifax might get a few likes from people on Twitter for being stunning and brave, but they’re losing customers and they will eventually have to explain this to their board.
The problem with this sort of argument is that it sets up a straw-man, without describing what you should do instead. Kubernetes could be better - of course - but what better approach is the author recommending to use instead? It would be better if we could use one language on frontend and backend - of course - but what is this one language that works everywhere? It would be better - of course - if there was a SaaS that could do everything for us, is cheap and is open source - but what is that SaaS?

It's very easy to say something could be improved, but much harder to propose something to replace it that doesn't have its own shortcomings.

It's a pity because this article actually makes a good point, that we should think about what the actual user/business goal is before making technical decisions, and be careful lest we spend all our time on technology. I've heard this idea described as "innovation tokens". It's disappointing that the article chose to wrap this idea in clickbait, but I guess we wouldn't be talking about it otherwise!

Disclaimer: I have no end of personal biases in favor of kubernetes!
When I say sleep I mean that you listen until a timer runs out and it pauses whatever you're listening to automatically.
gay and queer are not offensive even outside the community. It is acceptable for other people to use them. I haven't heard fag used non-offensively even inside the community, but maybe that's what needs to happen. Personally, I think it's great and that's what should happen to all slurs. They mean after all just "X but bad". When you turn them into just "X", you disarm the offenders and so the trend loses its memetic ability to replicate throughout tribes, and so people are less likely to denigrate only to assert their position as part of a tribe.
I think the Go reference was designed with learning users in mind, whereas the Rust one isn't. That's where the book comes in; it's a more structured way to learn the language than just reading the reference. The reference can be supplementary, thought.
Guide her to https://en.wikipedia.org/wiki/HowStuffWorks
I think if you're in the front end world and likely to do more full stack work go is perfect for this, so its likely to lead to jobs in the next year or so.

Rust I like it but worry it hasn't really taken off as I expected. C++ seems resurgent. The C++ world is vast, perhaps you'll learn more with that and the skills will be more useful. Either C++ or Rust dont get used in full stack though so it really is a different world.
> Hermetic build systems

Wanting to know more, I found this:

"Hermeticity: This page covers hermeticity, the benefits of using hermetic builds, and strategies for identifying non-hermetic behavior in your builds."
https://docs.bazel.build/versions/main/hermeticity.html

Sounds great.

Ages ago, my teams had a policy of "one button build". Install VS C++ on a new box, open the project (from source repo), hit "Build". Tada.

We could rebuild any revision on demand. Terrific for reproducing regressions and delta-debugging.

In the Java world, with (misuse of) maven, gradle, jenkins, etc. attaining reproducible one button builds is quixotic.

For hermetic builds, everything would be digitally signed (SHA256), right? There's a spec for signing Linux kernels, which I can't quickly refind. But the idea is to apply that strategy to everything, right?

That sounds perfect.
If you look to glue systems and add some new code at system level (not confuse it with OS level), the Golang is a better option. E.g. microservices, talk to databases, implement some distributed algorithm in your code.

Now if you plan to do number crunching, low level algorithm or scientific computing, Rust by all means. Unless you glue algos, then Python or Julia
UMass Lowell has a 1 MW UMLRR nuclear reactor: https://www.uml.edu/Research/Energy/research/nuclear-energy....