skysight-inc/HackerNews huggingface dataset:
> No, in practice humanity never figured out how to safely and efficiently use this power source and now renewables are a way safer and cheaper bet

Take a look at Ontario's power generation data right now: https://ieso.ca/en/Power-Data

We have a steady state of about 8.3 GW of nuclear power generation as our base supply of power, representing most power generation in the province. Electricity prices are pretty good- but they used to be better even before it was all privatized. The CANDU reactor design is safe and practical.

We can't rely on solar this far north- the days get too short in the winter. We have wind, but it's too unstable to be a sole source. You can see in the graphs what happens when the wind dies down- we fire up the gas plants to make up the difference.

We have hydroelectric dams, and they're wonderful for variable supply- like a self-refilling battery- but we only have so much capacity there without damming the whole province.

In conclusion: we have figured out a way to safely and efficiently use nuclear. Renewables are cheap, but not steady enough to be usable here. The alternatives are fossil fuels. Nuclear works.
Low-Cost Drones Learn Precise Control over Suspended Loads
> Homes in Hokkaido area, where it gets quite cold in winter, have good insulation.

Define "good insulation". I live in Aomori prefecture and most houses here have terrible insulation, and when I visited Hokkaido it didn't look much better. There is a reason why home centers sell lots of different materials to insulate the house yourself, because the construction itself is awful.
Thank you for pointing this out. It obviously can't be his first C compiler because it's written in C! :)

I'm not even sure it's the first C compiler written in C, though - it just says in the github description "the very first c compiler known to exist in the wild."

Regardless, if it's from 1972 it's a very early version.
Just because cars are fungible to you, doesn’t mean they are to other people.

The same applies to domains. Some people don’t care if they need to add an extra word, or pick a different extension. To other people it matters a lot.
Hmm, I see them participating on linux-arm-kernel list, nothing since January though:

https://lore.kernel.org/linux-arm-kernel/?q=corellium
So the two-word title here already failed? Hmm.
Same experience, though I never tried to get a discount out of it.
> I'm being hired because the bulk of my experience is applicable to the role, but, I can already foresee there are blind spots that I have that will make this job challenging.

Sounds like you need to cut yourself a little slack? No one is hitting the ground running from the get go when they are first hired. You will learn the domain and gain more experience over time. Some day you will move to a new org and the process will start over again.
If you're interested in the economics and history of home construction, with a focus on different levels of prefabrication, Brian Potter has a very relevant substack. Below are a some articles I think are relevant to North Americans looking to understand the state of prefabrication:

[1] reviews prefabrication systems, broken down by technology. The conclusion suggests it's difficult for these systems to reach the scale necessary for success.

[2] explains the primacy of balloon frame construction in North America through the frame of "worse is better."

[3] most recently, a survey of componentization technologies.

1: (Two parts) https://constructionphysics.substack.com/p/book-review-indus... and https://constructionphysics.substack.com/p/industrialized-bu...

2: https://constructionphysics.substack.com/p/balloon-framing-i...

3: https://constructionphysics.substack.com/p/building-componen...
IMHO there are non!

Through there are mono colored languages.

E.g. go would be mono red.

Normally mono blue languages allow you to "emulate" red contexts using callback's, listeners and similar. So some would argue there are no mono blue languages.

Many of the points (like red being harder to use) are 100% language impl. dependent.

The only think which is generally true about coloring is that mixing colors is a bit harder and sometimes can be sub-optimal for performance. But how much harder depends fully on your programming language and use-case might be negligible. Same is true for performance.

Also the two big problem of mono red languages is that while red has less overhead when a lot of parallelism is involved it has more overhaed if little parallelism is involved. And that interacting with other programs using a FFI conceptually harder. Which can lead to a varying degree of complexity and potentially performance drawbacks. But again how much this matters is again very language and use-case dependent.

All kind of tooling (including type checking) can reduce the drawbacks of either model (but introduces new drawbacks like longer compilation times).

As a side note: Communicating between red and blue functions is only potentially hard when they call each other. In the same way mono-red languages have only problems with external programs if they communicating over a FFI. If things like futures, streams, channels or similar are used (assuming proper implementation) red and blue code can normally communicate just fine, even if run in the same process.
It depends on whether the PD controller chip supports sending SOP'DEBUG/SOP"DEBUG packets, and, for those that do, whether it is exposed to the host OS or the firmware running on it does so.

However, even once you have that working, you still need to connect the other pins to a serial port adapter, and I don't know if any other laptops implement this in a compatible way, so you would probably still need some kind of cut-up cable that breaks out the serial wires.
> Ask a non-golf player what is an eagle or ask a physicist, a mathematician and a politic (sic) the meaning of power.

All those fields could do with less jargon. Especially since in many cases there is a common word.

Lawyers especially give me the impression that they use jargon to obscure their field from regular folks.

Our field, being new, should not make the same mistakes, but yet, here we are, where the default "file viewer" on Unix is cat, the pager is called "more", etc.

I don't see any reason why those types could not have had descriptive names from the start. Well, there was one, lack of experience, so ¯\_(ツ)_/¯
It’s pretty common to not show ‘Enterprise’ level pricing to the public. It’s all going to be different depending on the customer. For everyone one else, it’s free, awesome! What are you expecting to see?
You can get a rough measurement of the scale effect by comparing Hinkley Point C and Olkiluoto with cost of new VVER plants and time which it takes to build them.
> Also, most programmers know zero about computer science.

What made you say that?
Economically viable because the costs of the land used behind the dams were not nearly as high. Today most of the good places for hydro are already taken, and we have far more concern for the environmental impacts. There is still room for adding hydro, but it isn't as easy as in the past.
This seems naive. If you have a brain and you make a digital copy of it...you now have two copies (assuming you can even make a perfect digital copy, which seems doubtful). What does that mean for continuous experience? Who are you at that point? WHICH one are you? Then you kill the first one...effectively murder. Philosophers have never been credited with their practical abilities...only theoretical.
Achieving simplicity is hard. Allow me to explain, with a software analogy, too many times "customers" or users wants a "simple" solution, wrongly expecting that a simple final product was made with a simple implementation, which is not the case at all. It's the opposite.
I would expect the same process about writing, a final and concise essay requires tons of work, removing a word and replacing it with a common alternative and rewording phrases to make it simpler (for the reader). I understand Paul statement as "use a limited and common vocabulary" rather than complex words and sentences with fluff.
Off topic, but thanks Wolfram for creating Golden Layout. I've developed two major platforms using it, and it's been hugely beneficial to the systems I've built.
If you can read German, I recommend the Dr Oetker Schulkochbuch (1952 edition), the reprint is available on Amazon: https://www.amazon.de/Schulkochbuch-Reprint-von-1952-Oetker/...

It explains all these things, even what a pinch is, how to use a stove, everything you could ever need in the kitchen.
Hierarchy Is Obsolete
I must be out of date, because that just looks like a guy with a hat on to me. I thought hipsters were into dressing ironically hence the neon I typically picture when remembering people from college. Has the meaning shifted in the last 10 years?
You can find our architecture graphs under this link, make sure to checkout the subpages: https://docs.webiny.com/docs/key-topics/cloud-infrastructure...
Pretty great. This is how I would like to work, too.

Of course, it would be nice to know how much money the author makes with this product...
I'd be a bit wary of something as important as invoices on the Rpi storage though. Hopefully there's some automatic backup.
True - but the datacenter burning still hits you where it hurts if your entire Kubernetes cluster is living in that datacenter.

Whereas if you make a point of spinning up each Linux box on different datacenters (and even perhaps different providers) you are at least resilient against that.

Using advanced tooling doesn't remove the need to do actual planning beyond "oh I have backups" - you should be listing the risks and recoveries for various scenarios - though being able to handle "AWS deleted all my servers because I returned too many things via Amazon Prime" means you can also handle any lesser problem.
I think the biggest 'externality' subsidy of renewables is exactly your point 3.

It's all well and good saying you can produce solar + wind en masse for 3c/kWh (even without govt incentives), but if you need to have a gas plant running extremely inefficiently to pick up the shortfall, I'm not sure you can say it is 3c/kWh.

I'm very pro renewables but think it is increasingly getting missed. You often see charts that solar/wind is significantly cheaper than nuclear, but never taking into account this.
Probably not run an email server. =[
I literally just finished a round of interviews and the interviewers had to call me on my phone because Webex wouldn't transmit audio.
This is a good point.
I wish there was more discussion around when to consider making these decisions, how to transition, what types of systems are in the middle ground between bedroom and facebook, etc.

It seems all of the articles/posts that get are attention are the "you don't need it ever" opinions, but those are incredibly short sighted and assume that everyone is recklessly applying complex infrastructure.

In general, it would be nice to have more nuanced discussions around these choices rather than the low hanging fruit that is always presented.
https://www.sciencedaily.com/releases/2017/11/171106112256.h...
Worked for me when I last tried couple of months ago, Ubuntu 20.04 with Firefox. But maybe I was being a test subject (since I am an employee).
“Easy reading is damn hard writing.“ — Nathaniel Hawthorne (apparently)*

There’s definite value to simplicity in writing. At the same time, like all principles, people tend to run with the idea and misapply it. There are some cases in which your work demands a certain level of precision that’s only possible using complex words or jargon. Not to mention, writing that’s a little complicated can be a lot more fun! There are several novelists, essayists, and poets who are a joy to read not because they express their ideas as clearly and simply as possible, but because they manage linguistic acrobatics that make us realize there are ways to use language we never thought possible—often it takes some extra work to understand such output.

*: Have never taken the time to verify this myself.
I agree. It is an excellent book that will teach you to use fewer and simpler words. I think it makes a lot of sense in technical and business writing.

Aside from knowing this though the most effective thing I've learned to do is to keep re-reading what I wrote. Reorganize phrases to keep connected thoughts nearby in text. In English you have a lot of freedom to put phrases all over the place in a sentence. When I write I very rarely put all the connected phrases next to each other in the first pass.

But I guess I'd generalize that to say: taking the time to re-read what you wrote and edit it actually makes a big difference. It took a lot of shitty writing and overcoming laziness in school before I learned this lesson.
It's not one that just recently had to start migrating from Flash, is it?
So what is different about an M1 that lets you do this without the serial port adaptor?
Most tools are easier than people make them out to be. The average dev just isn't that great, and the average company overestimates the difficulty of these tools, while burying their devs with mindless drone work so they never get the time to study these things. The average dev isn't one which has studied CS/software dev and/or spends loads of free time still investigating tech off the clock, either.
I think we all know that we should write simply, but not always what needs to be simplified in something we've written. I find http://hemingwayapp.com to be useful here. I don't listen to all recommendations, but it helps me fix some mistakes I make often - using passive voice, unnecessary hedging etc.
A lot of the comments seem to conflate three or four different things:

* built on-site vs. fabricated in (usually) a big woodworking shop

* built according to an off-the-rack architectural design vs. built to the architect and clients' desires

* finished with standard materials (on site) vs. finished with custom floors, kitchen cabinets, paints, triple glazing, whatever (on site)

* completely built (modular) units that are just moved into place -- rare, but it exists, e.g. container homes

For residential construction, as far as I can tell there aren't really any cost savings associated with remote fabrication, but the house might be up faster, quality control is a bit better and foul weather is less likely to mess with the schedule. However, it's completely custom, with no limitations whatsoever. The shell itself might be prefab, but it will be finished on-site with a brick facade or render or wood boards or, heck, quarried stone if you like.

Using a standard design as well as the builder's default choice for your tiles, cabinets, toilets, what have you, will save money because these "start to finish" builders (or sometimes general contractors) buy in bulk and pass on some of the savings, but the more you want to customize, the less you save.

The article talks about a very specific kind of prefab that is highly standardized but where nevertheless even the floor plans can be customized, albeit limited to certain standardized sizes and a small set of options, sort of like how you buy a car.
Congratulations on the launch! This sounds awesome! Sounds like it could be very useful for taking some out of the complexity of orchestrating the various serverless components. I am very curious, and looking forward to trying it out!
That's kind of not a language-level thing. I mean it is, but it's tied very very closely to runtime choices rather than the language itself.

Basically your question is equivalent to asking whether the language has green threads. The original article describing color (http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y...) says it's just threads, but it glosses over why a language like C# decided to add async-await and why Java now has its ongoing Loom project.

System threads are heavyweight and as a result usually unsuitable as your concurrency primitive for highly concurrent applications (although you can and most runtimes do build on top of threads). And so if you only have that, you inevitably get what the article calls the "color problem" (see e.g. in Java the async IO APIs, which the article laments, but doesn't explore why they exist and moreover are often preferred by Java programmers over their synchronous equivalents), because system threads aren't enough and a color-based solution inevitably must appear on top of them.

So the question to ask is "does Nim have green threads?" To which the answer is no (and then by extension it does have the color problem, in this case via async-await).
De-Duping the Duplication in Services Featuring: OpenAPI and AJV
I confess to having played that game in the subway. Never with bad intention, just bad manners and curiosity on my part.
Thanks, i've overlooked that

var mask = VectorMask.fromLong(SPECIES, 0b0111_1111);

var i = 0;
var upperBound = length - length % 15;
for(; i < upperBound; i += 15) {
v1.intoArray(result, i);
v2.intoArray(result, i + 8, mask);
...
Doubtful. The consultant who is willing to say that straight (and with the experience to know it) is going to be worth a lot more than $200/h, to the right clients.
That really depends on the interest rate, your familiarity with the investments, your debt/asset ratio and your expected ROI.

I would argue every mortgage, real estate loan and small business loan is borrowing money to invest.
Tons of work done in various industries is "shitwork" that the person doing the work wouldn't normally do except they're being paid to do it. At some point you give up arguing with the customer.

The dieting is a perfect example - many health issues can be solved by losing weight but few people want to make the lifestyle changes necessary to do that.
That's what I meant by "no persistence needed". In both cases, I wasn't actually saving anything to disk. I needed an in-memory storage for a never-ending stream of incoming data that would be read (and purged) by a separate process, no biggie if the data got lost occasionally.

I also simply inserted and read the data, no complex queries or anything. Key-value store is all I needed and for this particular case PostgreSQL was as good at it as Redis.
Syncthing Untrusted Device Encryption
> To begin with houses in Japan are usually not built to last because typhoons, earthquakes, fires and mud slides have historically destroyed them in the course of a few decades.

other reasons that resale homes are not very good business in Japan:

- Japanese believe it's not clean to buy a home others lived in before, they obsess over ultra-modern brand-new places the same way Apple fans like their newest gadget.

- houses fully depreciate in 2-3 decades

- ghosts (this is not a joke. it includes the believe that the house isn't just an object but has a "soul" (this believe extends to cars and other inanimate objects))

See also https://holdblog.com/resale-homes-are-not-a-good-business-in...
Well talk about strawmanning, who said you couldn’t have a corner of the internet? There are plenty of TLDs that aren’t subject to the issues .com has.

Sorry but yes, if you’re not making enough money from your .com to pay (say) $50/year, I think it’s perfectly fine that you can’t use it for your random hobby project. The lost value that comes from .com being messed up is so much greater.
Ask HN: PC logistics for remote employees – cloudy solution?
We need to send computers to new employees, and sometimes get them back after they leave the company.

Is there a service that to me looks like the AWS console, but in the backend procures new gear, provisions it according to a spec, ships it to employees; and at the end of employment sends some prepaid return boxes and collects the stuff.

Ideally globally. Ideally can also store some of company swag and send that along :)

(I'm not asking about MDM etc., just the physical aspects of the work)
Now, do us a favour, and tell us how that is not possible.

You are embarrassing yourself here with lack of manners, and constant attacks. Behave yourself.
Reusing instead of producing new also is very high up on the reduce-reuse-recycle order. I don't have figures on at what point it's better to upgrade to more efficient processors than to keep using older ones that were already meant for mobile devices, I'd be interested if you do.

All I was saying, though, is that you can have dedicated hardware at almost zero costs and without having to use a party like Oracle or Amazon.
The Digital BOR
I think HG Wells would see the irony...
My domain ends in .me which according to Aliexpress is not real. So instead of me having to manually unsubscribe, they got sent to the huge spam box that is gmail.
But that's exactly what surgeons and accountants and mechanics and consultants and entertainers do. Most work is unnecessary. Once you embrace that, it is a lot easier to understand how this economy works.
Operations guys, "devops" as they are called now, remain the arch-wizards with grey beards. They love creating highly company-customized, incredibly complex, often times brittle infrastructure and deployments based on obscure scripts written in non mainstream languages based on plugins and libraries without documentation. The same opaqueness as in IT security, but in emergencies you can downsize/ignore IT security, but without the ops guys your product can not survive.

Kubernetes, Helm and cloud-platform specific quirks were a godsend that cemented in this status for at least another decade.

There is probably no job with higher job security in tech than this.
As usual, xkcd is relevant: https://xkcd.com/547/
Current UI/UX dogma is tainted, to put it bluntly.

It's been A/B tested and optimised to death not to empower the user, but to disempower them. The push to get the user to click on the "subscribe"/"buy now" button, or to stay engaged with the app so that you can keep pouring ads down their eyeballs, is an overriding concern.

In contrast, 90s/2000s research was all about empowering users, acknowledging psychological limitations so that you can work around them to let people work more efficiently, and making your workspace/playspace your own. Modern UI/UX is a near opposition of that.
The internet is also a public place in many ways. If someone overhears my name and sees my face and discovers my personal website or LinkedIn page, then they have only discovered MORE public information about me. There is no privacy breach if I don’t divulge private information on public spaces, i.e the internet.
This isn't totally related to infrastructure but figuring out what you should build, from what you could build is something I've struggled with as I've moved about the engineering management ladder. My current role is a stone’s throw from solo developer (only developer at 4 person start-up) and while I've got total autonomy in the work I complete and the approach I take, it’s a terrible feeling discovering that you're not super-human and you need constraints like almost every engineer that's come before you.

Like the author there's been a number of times where I've felt self-satisfied completing a piece of technical work, only to scratch my head a week later and wonder whether it was worth it. I can say with certainty that having a solid CI/CD pipeline has saved my bacon a few times so I'd probably recommend that as an early investment to make, internal tooling for some of the customer registration was a bit of a mistake and not as critical as I thought it would be which now feels like a waste of 3 weeks.

I am yet to come up with any meaningful advice to pass on to developers in the same position. With time you get better at spotting when you can get away with hacking solutions together and when to put the time in, having a forward vision for a product really helps on focusing your thought and attention and time spent on making things visible to the rest of the business is rarely time wasted. Awareness of what’s going on with the rest of the industry is useful, but don’t obsess over the new hotness, build with what you know works and save your innovation tokens for a rainy day.