skysight-inc/HackerNews huggingface dataset:
Sad to see another article that gets the roles of those involved in the creation of the 4004 confused. Wikipedia gets it almost right:

> The chip design, implemented with the MOS silicon gate technology, started in April 1970, and was created by Federico Faggin who led the project from beginning to completion in 1971. Marcian Hoff formulated and led the architectural proposal in 1969, and Masatoshi Shima contributed to the architecture and later to the logic design.

Need to add that Stan Mazor worked with both Hoff and Faggin on the design.
Selecting a language is like selecting a tool. It would be worse to select a language that on first sight fits the problem if you don't have any experience with it.

To be honest, today there are many viable solutions with different languages. I would not recommend to start with a plan where you have to reimplement the system in another language at some point. Experience tells me that almost none of such projects survive.
Where does the author imply something like "Pick python no matter the .. etc.?"

I read it as the much more milder "don't reject Python because of vague concerns about run-time performance".

I can't find anywhere which suggests the author things people should use Python to, for example, code up their web app front-ends or to implement a 'hard' real-time operating system.
Agreed. Mobility and structural elements combine poorly.

Far better reliability and use of space would be to provide a standard structure, insulated against winter, with flexible shades and blinds, and then use the additional space to provide patio or porch space which could be opened more fully or closed in given precipitation, sun, and/or weather.

First time you forget to close up the house before a surprise snowstorm will be a memory for the ages...

Not nearly as flashy. But vastly more practical.
Yandex Taxi in Russia
Has anyone used this wonderful cab?
You also tend to pay for the privilege of a 5 year fix (as a first time buyer) - about a 0.4% increase for a 5 year vs a 2 year for us.
Thanks for the thoughtful bit of commentary! It's true, my disproportionate focus on embeddings and no explicit links might have been just an extreme reaction to the current state of tools for thought which are 99% graph-based. Was curious to see what would happen if you only relied on those. Though I agree that explicit links are sometimes handy and can code useful information, so I'm also excited to see more of this interplay developing in the future.
They might not be able to solve climate change, but they can for sure slow it down by kickstarting geo-engineering efforts. They may even be in a better position to do this than nation-states.
They absolutely love adding them to previously functional systems even so!
It's more than that. For example, converting a string to uppercase in C++:

#include <string>
#include <cctype>
#include <algorithm>
#include <iostream>

int main()
{
std::string s("hello");
std::transform(s.begin(), s.end(), s.begin(),
[](unsigned char c) { return std::toupper(c); });
std::cout << s;
}

Same thing in Python:

print('hello'.upper())
Actually, writing a POC or a MVP is quite different to writing a "long run" production product. In the first case, coding speed is surely a must - and any untyped (or loosely typed) language might be good enough - but in the last case, when dev teams have to maintain some code in the long run, during multiple versions, with turnover, typed (or pedantic) language might be easier to work with because the language already include some kind of documentation (types) and automatic checks (type verification).

Moreover, the availability of "average" (and "cheap") programmers matters a lot in the long run: if only genius can maintain your system, then you'll have problem in the long run because you'll either need to keep them at all price or need a lot of time to replace them. So, in the long run, you should better use a wide audience language with a lot of available programmer (even if they are "average") than a specific language requiring good programmers. However, for an MVP, you can recruit a genius programmer using the fastest tool for the job.

Obviously, some domain are more oriented toward some language... and for ML for example, python is quite a good choice because of the libs (as Java could be for - lets say web servers)

So it matters a lot what your system will be used for and how much time you will require it to run before needing to rewrite it from scratch
Down vote all you want but when your wife asks you why you don't have a TV in your brand new house you're gonna cave like a deck of cards in a hurricane.
That's what I thought when I was 24. By 34 I bought the house I'm writing this from for what I thought was an extravagant amount of money, and by 44 I'd paid it off. It is now 3.5x the price I paid. That price was 2x of what the original owner paid a decade before me. I did have some money when I bought the house (obviously) but it still seemed insane. And I think that's actually sort of by design. It's the largest purchase most people will make in their lives, and there is one million ways to screw it up, so of course it feels insane and uncomfortable. And yet, people manage to scrounge up enough money and courage to buy real estate somehow.

Which is to say, if you're on this site, chances are you'll be able to afford a house, just not at the price you like. Your income will track inflation much better than that of Joe Autoworker or Jim Farmer.

The big downside for you is going to be that most tax brackets aren't revised upward with inflation, so you might find yourself paying nutty effective tax rates that you're voting for right now. :-)
> Programming culture is more about memetic and shared ideas and uses tradition to select winning strategies.

Sounds exactly like business management culture. Makes sense though, developer productivity is first and foremost a business management issue so discussions about it ought to follow the same path as business management. And business management love their anecdotes, great person citations and jargon.
There’s a lot more expenses as a homeowner than the mortgage (even the PITI (principal, interest, taxes, and insurance)).

I can’t think of a year where I didn’t have $5K of crap that needed fixing/replacement/improvements*, the year with the fence was 6x that, and I’ve got a boiler coming due that will be a $15K project in all likelihood, $25K if I go higher-end and improve the piping configuration for more even heat on the far end of the piping runs.

* not making improvements is a major saving point in favor of renting. Improvements are a money and time pit and most return less than $0.50 per $1.00 spent on them. It means you live without the improvement, but it’s wildly less expensive over time.
Don't be fooled, companies can absolutely sue their employees especially in regards to trade secret theft.
Only because it happened once and then they fixed it, but it was never a problem in the old days. Having one company and one package manager act as a single point of failure for essentially all of the javascript in the universe was a bad idea.

It looks and feels a lot more like "real" programming now but the whole house of cards seems to tip over and burst into flames every other week.
Redis Streams vs. Kafka
Well, part-time programmers. Full-time employees, doing mostly semi-academic stuff.
Do people dislike wireless or do they dislike Bluetooth?

Because Bluetooth sucks. It's a shame it's the industry standard.

Bluetooth support is still spotty on Linux, which to me is continued evidence that the stack is complicated and bug-ridden.

Even for my high-end BT devices, there are still lots of problems. In addition to the problems listed elsewhere in this thread, I particularly have problems with:

* Easy, reliable switching between connected devices.
* Reliably connecting when a device is turned on.
* Audio delays on the order of 200ms.

I stick with wireless almost exclusively, because I hate the wire, but I switch to wired for gaming because a 200ms audio lag for a real-time game is unplayable. 200ms is obvious even just watching someone speak in a video.
The negative externalities are too many degrees of separation and to many years away from any immediately obvious perception of harm.

"Officer, these men are stealing my lawn, a few blades of grass a day as they walk by!" This doesn't engender a threat response until there's visible damage, and even then the solution is likely to involve signs and warnings, since the responsibility for total damage is so widely distributed. We need a fence around the climate lawn, and we can't leave the gate open for some people and not others, if you catch my drift.

We're beginning to see global acknowledgment of the problems and gradual progress towards reducing emissions. Once technology can accurately measure the cost of the negative externalities, they can be priced in. If the cost is on an exponential trend, where each ton of co2 is now seen to cost the operator an additional .0000001 cents, but 100 years later might cost millions, with regards to preventable damage, markets currently are accurately pricing in the costs. They're just not equipped to assess global climate and long term planning as relevant. That has to come from legislating sane and scientific and fair rules.

There's nothing inherently wrong with burning coal if there's a globally recognized system of accountability. Since there's not likely to ever be such a hegemony, you get what we have now - slow, frustratingly bureaucratic incremental progress, and therefore the need for mitigation as well as sustainable energy tech.
A rock has a precise definition. And there's strong evidence to support that statement. For example, many species can be taught to distinguish, say, rock from food.

Consciousness does not have a precise definition. It's a very nebulous concept.
Suicide is the best thing Californians can do to better the world.
.. And would you categorise those different dysbiotic states into ... types?
I think a large part of the difference is the prototype vs prod. I have written prototypes in C++ in a few weeks that still took months to go to production. It is just that production-ready code require significant more ceremony, more config files, more complex error handling, code reviews and of course feature creep.

I still agree that Python can be much more efficient to write than C++. I just wish it wasn't so unbearably slow.
I agree your generation is pretty f-ed (even here in "socialist" Netherlands) and I hope they will raise taxes on my generation until something good can happen for yours. At least here they are really cracking down on my generation owning multiple homes and renting them to yours for a super high price, among other things.

That said, your generation is digital native, you don't need to live in an expensive city, you can collectively decide to work remote from cheaper (and perhaps more beautiful locations). Our generation will eventually start dying. You need to be creative. I'm sorry. Tell me what to do...
The research on this topic has been discussed on HN multiple times. It is indeed hard to look up previous discussions, but the conclusion is always inconclusive... one thing everyone seems to agree nowadays is that measuring LOC is a bad proxy for programmer productivity, specially when you take code maintenance into consideration (which very few research papers do), and that types do have a small, but measurable effect on improving quality (though whether that's at the cost of productivity is still unclear as far as I know - yes, programmers need to spend a bit more time to declare their types, but without them they have to spend more time every time they need to call anything).
I live in San Francisco, so I probably can't directly compare my situation with yours (I assume you live elsewhere, somewhere with even lower density). I moved here 11 years ago, in part because of things that no longer exist here because of rising property costs. I've watched my favorite restaurants, bars, and shops close because they couldn't afford rent anymore. I've seen great people move away for the same reason.

Also consider that last bit: how many people have had to leave your town because newcomers have priced them out? It's not just new people moving in who are upset with higher housing costs.

I like density. We don't need to turn into NYC, at least not into Manhattan. Brooklyn's density allows for a ton of 2- and 4-plex neighborhoods, with some SFHs mixed in here and there. Their density is at least twice that of SF's. If you want to live in an urban environment, it's ludicrous to expect any significant amount of single-family homes. And yet SF has square miles of exactly that.

The thing is, you can't snap your fingers and make housing demand go away. This is the thing that baffles me most about all the opposition to new housing here. It's like people believe that if they just stick their fingers in their ears and yell "NA NA NA NA GO AWAY NA NA NA" for long enough, all the newcomers will just go away. And maybe they will, in a few decades, but the increases in property values will go away with them. Which is funny, because as much as you talk about "character", the main reasons I see people wanting to "preserve their neighborhoods" is to preserve their property values.
We typically track many things about the activities in the queue, and we want to summarize the results by choosing a shortlist of the most relevant ones for our projects.

Dμ = Delivery service rate. Devops teams may say "deployment frequency" or "we ship X times per day".

Rτ = Restore lead time. Site reliability engineers may say "time to restore service" or "mean time to restore (MTTR)".
Justification: India was one of the richest countries in the world before the industrial revolution. After years of invasion and loot it was left as one of the poorest. Western countries have built their economies on coal for over 100 years and got rich and still use per head more than India. EU/UK/US carbon output per person is still much higher. Now when India is growing others are telling it needs to change. Well you thrust it upon them, now we can fix this if you fund Indias change and invest to change, otherwise it can't.

More info: https://www.bbc.co.uk/news/av/world-asia-india-59049691
I used to run around the big tech shops with my phone and took photos of the Windows Licence sticker (WinXP and later Win7) to have enough keys for my experiments.
> should be readable even in a compressed js unless they run it through an obfuscator

User-Agent may be determined on a webserver/proxy level and request redirected silently to a page with JS just showing the banner. It does not have to be based on JS checking anything.
I saw a piece of research saying that it is true, that depressed people see outcomes more realistically, while non-depressed people are in a state of constant self-delusion where they convince themselves things are better than they are
> I don't know a single highly experienced multi-lingual developer who does not reach for a dynamic language when they need to deliver something quick and easy.

If you're picking from a popular language, the language itself rarely matters for this at all. Every popular language does roughly the same things. Writing speed (length of keywords, for example) is a non-issue. The ecosystem is by far the most important thing.

It doesn't matter how efficient I am in Go if I'm missing a crucial library that I'll now have to write myself.

JavaScript is a classic example where, even if you are pretty fast at writing your code, you will be dramatically slowed down by: 1) needing to add a new package every 5 min to do something trivial, 2) looking through five half-dead libraries to find one that seems maintained and usable, and 3) finding out that some of the libraries you chose are buggy.

So for a quick prototype, I'd weight a language's qualities as follows:

- ecosystem: 90%

- static analysis/tooling: 5%

- stdlib: 3%

- syntax: 2%

And for a long-term, complex project, I'd weight them closer to:

- ecosystem: 50%

- static analysis/tooling: 46%

- stdlib: 3%

- syntax: 1%
Over time I've come to conclude we are not optimizing for language features, we are optimizing for the community around a programming language or stack.

Sure, features are important and if critical ones are missing it might be a show stopper. So there is an initial thresshold that all candidates must pass.

But problem solving is not a one-off exercise. It tends to be both dynamic (=facing unpredictable challenges) and recurring over long time horizons. Which means having a healthy, engaged, resourced community that will invest in adapting / solving future requirements is essential.

So the "optimization" problem includes quite a bit more than the presently known developer team, its software stack its hardware and current problem definition / user requirement.

I think you see this dynamic in several cases (including python) where you might not think that it makes rational sense.
Who says the goal was to disprove? It's just extra data.
Patching the Tangent Quattro Reciva Radio
China is changing extremely quickly, but it isn't enough to simply look at imports vs. exports, but also the kinds of products being exchanged. China still produces more cheap and dirty products than it imports, so the net emissions considering imports/exports are lower than gross emissions. The trajectory is clearly in the direction of more emissions for consumption though, which makes sense as China is still growing richer quickly.
I agree that it's fun to read about automation workflows, I like yours too.

Using highlights, notes on Kindle and exporting `My Clippings.txt` opens a wide range of possibilities and should address your problem too.

It's too bad that Amazon doesn't store the highlights, notes in the .txt file on its mobile apps and the cloud sync works only with the books bought from Amazon; Though individual highlights/notes can be exported as .html from each book regardless of where the books is from.
The intentions there are good, but reads bit unrealistic in some places. Being a boomer, author doesn't realise how far financially he is then many people who are younger.

> Stop wasting your time on commuting, boring jobs, meetings, TV. Do only things that you feel are worthwhile, with people you like. If this means a cut in income, so be it.

TV - sure, commuting - thanks to COVID only, the rest - sorry, but I would like a house/pension/family.
May be OS with small userbase and less popular browser combo.
It is my example, I can set the variance to whatever I like. It is a D/D/1 queue in case that isn't abundantly clear.

Which, in practice, is a model of queuing systems that often gets most of the value of queue theory and is easy to explain without jargon. Then apply an 80% fudge factor. Unless the situation needs care.
> Also as someone who lived in both the UK and now a Schuko country, I do sometimes miss having a switch on the socket :-) We have a floor lamp without a switch, so we have to physically unplug it to turn it off.

I've actually heard Americans make fun of our (UK) switches on the outlets. Usually something to the effect of "need to make sure the electric doesn't escape, when things are unplugged, lol". It completely misses the point. The point of the switches is we have a way to isolate a device without unplugging it. Without the switch the only way to isolate the thing is pull the cord out of the wall like some kind of neanderthal.
"Build global technical talent acquisition operations"

Why they think this dehumanising language is okay? It reeks of modern slavery.
> All the new connectors are for digital connections.

USB-C headphones might disagree with you, as the other comment has pointed out (USB-C supports analog audio on data pins in order to create the one-connector-to-rule-them-all).
Syncthing is actually pretty great for this purpose. I used it to keep my music collection, pictures etc. synced between my computers and my phone.

Nowadays I use nextcloud, mostly because it allows easier sharing with third parties and comes with calendar etc.
Being a software developer, I keep seeing bluetooth audio as a Rube Goldberg machine. It's using a battery that you have to keep charged, a lot of software, multiple CPUs, lossy codecs, forward error correction, and an entire stack of mind-bogglingly complex protocols (that no one has ever implemented 100% correctly) that run over an inherently unreliable medium so what? So you don't have to untangle the wire? It never made sense to me. I've never really taken bluetooth seriously. To me, it's a tradeoff that I just don't see ever making. I don't trust software this much. I also prefer something that's easy to troubleshoot when things go wrong.
I've done big desktop program in python. For some parts, we just used modules written in C, because code was easily 20 times faster than python, I was even surprised at how fast simple blits could be on modern hardware without any graphics card acceleration. But python version was several times faster to write.
Coal ash also result in more uranium pumped into the air as well. Coal, through the various damaging substances we pump out, kills more people every year than all nuclear accidents combined have killed going by worst case estimates. Very few things have a lower death toll by energy generated than nuclear, but whatever one thinks of nuclear, coal is truly nasty. You could have a Chernobyl every year and it'd still be better than coal.
I agree with the author on the server part of. It makes sense to make use of something specifically designed for the task at hand.

At the same time the post brings back memories from university when my fellows had these immature arguments about how PHP is the worst language on the planet and it shouldn't be used for anything but as a bad example. It's such a waste of time.

Some arguments of the author make sense in certain contexts, especially if you're used to do things in a certain way and you get other results in JS which is a different language, in a different context (the context being that JS to the web is much closer to what Lua is to game development than let's say Java to backend development). At the end of the day it's just lack of understanding that raises confusion. Only because something is "weird" it doesn't mean it's also bad.
> The problem here is that you can't really build "affordable housing" any more than you can build "affordable cars".

But you can? There wouldn’t be affordable taxis in Russia if there were no Kia Rio. You can’t just flood the market with government-mandated Mercedeses and expect good things to happen.
> Yeah, let’s kick old ladies out of their houses so we can get a piece.

If the problem is "kicking old ladies out", why not just allow seniors to defer their property tax, instead of what we have now, where even corporations pay the same fixed tax? Seems a little absurd to give the entire state a tax break for a problem that only effects 10% (at most).

The "old ladies" argument was just a cover for the real reason, and you've been duped.

> I’d like to see an example of increasing taxes on a good or service somehow making it cheaper.

It's fairly well known that a land value tax actually has negative deadweight loss, because it incentivizes more efficient land use. It definitely can't make housing more expensive, since the supply-demand curve remains the same (the supply of land is fixed).

Also: http://www.savingcommunities.org/issues/taxes/property/affor...
None, all the other hypothesis are second order effects. Weak genes are genes that do not reproduce.
Show HN: Turn articles into audio with a human-sounding voice