Hacker Newsnew | past | comments | ask | show | jobs | submit | ReactiveJelly's commentslogin

"favored by the NPM package ecosystem"

Huh. My story is that 15 to 20 years ago, as a young programmer, I read some of Stallman's writings and I was convinced that copyleft was the only way to keep free software free.

Copyleft vs permissive seems like a "paradox of intolerance". There's no paradox. You cut down intolerance where you see it.

But then I'm a big skeptic and I'm always willing to believe that everyone else could be wrong. Which is not a great heuristic, except when you're actually right.


It's all just knockoffs of Skype and BitTorrent :)

I'm glad there's a competing Rust and Go implementation now. I like Iroh as a Rust user and having tailcat around doesn't hurt me


So a stronger type system in the boundary between Go and Linux would have caught this?

My reading is that this is entirely Go’s fault. In Go, there was a union of two different types without metadata to distinguish the two. The disambiguation was done by looking to see if the data looked like a certain pointer.

I think the reason it is a problem only in 32 bit systems is that the assignment setting the lower half of the data is a 32 bit op, which can overflow the 16 bits used, but won’t affect the other half of a 64 bit value. (Corrections welcome.)


It's 64 bits on both but only 32 bits were read on 32-bit systems. Two 64-bit values that were different were considered the same because only 32 bits were checked.

Wow that's a lot of snark


> Carve something into plastic, on the other hand, and it can survive decades. Substitute plastic for metal, and you just turned decades into centuries.

"I write these words in steel, for anything not set in metal cannot be trusted."


I've been saying for years that future archaeologists will wonder at these mysterious emblems they dig up, generally associated with a large deposit of what was once highly refined iron, aluminium and copper. About half a metre wide and 11cm high, made of incredibly durable plastic obviously intended to last for centuries, if not millenia.

And they'll puzzle over the inscriptions, "G809 BGG", "R420 BRL", "RFS 131Y", "SJ12 EXW", "RE51 CUE" - this on some huge chunk of steel, easily three times as big as the rest, and so many others.

What could they mean?


As a non-American, I don’t even understand today what that means. (And the website linked to isn’t loading, so I don’t have the context from that.)


License plates vary between countries but this description should be recognisable to most of the world.


We use "AA AA 1234" or variations of that, so the examples did not register as license plates at all. Interesting.


Regardless of the content, what other 50x11cm mass produced metal signs are there? I was thinking street name signs, before reading the examples.


The comment described them as made out of plastic, while license plates here are usually made from aluminum, so I was thinking more along the lines of some kind of packaging.


In the UK they're incredibly high quality perspex, to the extent that if you need to make up some small HV insulators that won't be subjected to a lot of mechanical stress you could do worse than chop up some old numberplates.


I believe those are car license plate numbers.


British ones of various vintage, with RFS 131Y the oldest of those, from 1983.


My old Volvo 340GLE 1.4, first car after I passed my driving test. Awesome things, engine at front, gearbox at back, 50/50 weight distribution, enough torque to break traction if provoked, inoffensive enough not to freak out your girlfriend's dad.

Perfect car for a 20-year-old.


"We believe they served some kind of religious purpose."


I mean, <gestures at car culture>...


Ironically, most of the metal stuff doesn't survive from antiquary. For instance most statues were in bronze not marble, but since metal can be easily recycled the only metal statues that survived are from ship wrecks.


Stone is a safer bet to survive the centuries, but even those are reused as bricks, like the Rosetta Stone:

https://en.wikipedia.org/wiki/Rosetta_Stone


I thought it was 40K reference at first about certainty of steel


it's from the mistborn series by brandon sanderson. fun books. would make a great big budget TV series someday


Mistborn was supposedly picked up for film.


Picked up by Apple, of all places, and Brandon finished the first draft of the screenplay last week.


You can buy rocks engraved with "Nothing Is Written In Stone". https://duckduckgo.com/?q=nothing+is+written+in+stone&ia=ima...


It is definitely a "Macbook Pro on a wooden table at a coffee shop, owner with tattoos and stylish facial hair" kind of website


Yea, but if I bought coffee table books and this was printed by Taschen, I'd buy it.

That typeface is so familiar. One imagines a great big red "reset" up in the clouds, benevolent creator pondering pressing, this is definitely the font on the button. I can smell machine oil, hear 50hz hum just looking at these labels.


> hear 50hz

100Hz, actually…


It looks like Go is memory safe for single threads and channels, but not for shared memory between threads: https://en.wikipedia.org/wiki/Go_(programming_language)#Lack...

> Go's internal data structures like interface values, slice headers, hash tables, and string headers are not immune to data races, so type and memory safety can be violated in multithreaded programs that modify shared instances of those types without synchronization.[113][114]


A land value tax would fix this


I know the Georgism joke here, but we don't need an LVT to fix this; we just need states to override home rule on minimum density requirements for residential and mixed-use zoning. The core problem here is in fact very simple!


Exactly. I have a plot of land in inner Portland and they won't let me build on it. I mean they will, but not at the density needed to satiate demand such that home prices fall to the proper amount a home should cost. Should be a simple proposition with someone trying to spend his own money to build housing but it's not because they make it as hard as possible.


Not on its own. You also need to relax or remove direct (and indirect, eg parking minimums) restrictions on residential density.


A land value tax without changes in non-tax land use regulations would not fix, and a land value tax would not be necessary after removing the non-tax land use restrictions which this responds to.


How?


It would allow housing to be substantially denser.


How would an LVT do that when the barrier to dense housing is zoning restrictions?

Changing the tax structure doesn't remove that restriction.


An LVT addresses the incentives underling zoning. The LVT imagined by Georgists would very probably result in radically altered zoning rules. Zoning, after all, exists primarily to prop up the finances of homeowners.


A Georgist LVT is based on the value of the bare land, which is constrained by permitted uses. Adopting it without first removing zoning restrictions would increase the incentive for homeowners to defend the existing zoning rules, since the removal of the rules would increase the scope of alternative uses of the land in ways which would make it economically impossible for most existing single family homeowners to afford the taxes on the property.

On the other hand, once you remove the zoning restrictions, the existing economic incentives will produce densification without LVT, tbat's the whole thing the zoning restrictions exist to stop.


I mean, I agree with you about zoning; we're fourth and inches from eliminating SFZ in my muni, and an LVT isn't going to happen anywhere, so the rest of the debate is kind of academic.


An LVT results in new McMansions getting built on quarter acre lots and being taxed at the same rate as SFHs and trailers on quarter acre lots. It's the perfect way to allow rich people to buy out poor people and pay the same tax as poor people. Welcome to unintended consequences. Institute an LVT if you want, but don't expect low cost housing to spring up.


> trailers on quarter acre lots

That is an irrelevant counterargument, since the idea of dense housing leans towards tall apartment buildings, not trailers. No one should have to live in a trailer.


The idea of what should happen is irrelevant, because we have not seen this "dense housing" actually materialize in US LVT jurisdictions any time in the past 100 years.

The township of the Fairhope Single-Tax Corporation near Mobile, Alabama was originally conceived as an artist's colony but is now occupied by families with a median income of $95K. Density is almost exactly 1 housing unit per residential acre. The feds have built 140 Section 8 subsidized units, but there do not seem to be any privately built high density tall apartment buildings of the type you want to see.

Can you point to an LVT place in the US where developers have chosen to build large numbers of actual NON-LUXURY high rise apartment buildings for the benefit of non-rich people? That would be a big newsworthy success story if it actually happened.

There are developers that make their money building high rise apartment blocks. Are any of them lobbying for an LVT so they can build more low cost housing?


> but there do not seem to be any privately built high density tall apartment buildings of the type you want to see.

There exist plenty of old buildings in urban centers that meet this criteria. There is nothing in principle that is stopping their construction. It's in the same imaginary league as LVT for that matter, meaning that if one can manifest, so can the other.

Luxury buildings are made because of a profit motivation. Even so, once the supply is increased by 10x or 20x, their prices too will come down. China is a supreme example of having cheap apartments.


The computer / phone should auto-detect and tell you on-screen


They've already done that afaik, like warning about charging at slower speed.


Some chargers will re-negotiate depending how many cables are plugged into the adapter. Which is fine, but sometimes makes it tricky to know if it's the cable, the plug, or the number of cables causing a slow charge


Haven’t ever seen a warning like that in KDE.


The hell Apple or Google cares.


Apple should care because customers will blame slow charging times and slow transfer speeds on the phone


I think Apple much rather tells users that this is exactly what they warned them about when they were forced to support USB-C and will advise users to only buy official cables from Apple.


You mean USB-C, the standard that they largely led development of?


No, they mean USB-C, the port they switched all but a handful of their devices to before any other manufacturer.

While GP’s take is ridiculous (if common), I do think the notion that Apple led the charge on USB-C is mostly a myth, outside of them being active participants on the USB Implementor’s Forum.


Eh, I can’t find it now so a thousand grains of salt, but I read a good article back in the day about how much Apple’s experience with in-market Lightning shaped USB-C’s physical connector and electrical handshake.


Today my phone said "Charging slowly" and it wasn't charging at all.

I miss MiniUSB. MiniUSB was always good to me.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: