1,337 karma · joined August 28, 2019
the same problem would occur if you tied to "sanction" some other open-source because china! oh, for example linux.
freedom, as in speech, is a double-edged sword. the bag, as it were, cannot be put back in the cat. what helps us, helps china. and what hurts china hurts us as well, maybe even worse.
it's no different than the physics that preceded the development of atomic bombs. the papers, the theories were public or semi-public all the way into the 1930s. germany actually helped the effort by banishing some scientists and by funding others. and then both groups collaborated internationally. once a weapon was postulated, and war was afoot, everyone made it top-secret. but the fundamentals were widely known by then.
it wasn't keeping secrets that won the race. it was the equivalent of spending the equivalent of 27 Billon dollars first that won the race.
so if you want to beat china in RISC-V, spend the money to develop it first, faster, better. throw 27 Billion into the development and do it faster and better than your adversaries. it 's a fair contest, so you better get to it.
"combinatorial logic" is cute, as is "CISC" and "chip" is epic.
perhaps England has a way of doing this. in the US it looks like https://en.wikipedia.org/wiki/Pruitt%E2%80%93Igoe
> 2. Rent control, rent control, rent control.
this doesn't work ANYWHERE and never has. it merely feeds scarcity and raises rents in anything economically or physically adjacent. it feeds urban blight, and does nothing to make private ownership more likely.
> 3. 100% capital gains tax
why? why would someone make an investment in something for 0% return? that's just entirely silly. great way to ensure that any good, mediocre, or even tolerable landlords exit immediately (being replaced by predators).
how about some taxes on non-owner occupied or short term rentals (Air BnB)?
maybe something like a land-value tax on under-utilized housing? with a close-to-ZERO capital gains tax. encourage investment, upkeep and providing housing. encourage vs. discourage sales to individuals.
graduated taxes based on number of units to discourage large holdings and encourage small.
take california where this kind of speeding is rampant.
- it has very regressive speed laws compared to other western states with similar roads. it has 55mph maximum for trucks (and cars) pulling trailers and on two-lane. 65mph anywhere else maximum. most neighboring states have eliminated split speed limits and have 75 or 80 max.
- it has a comparatively large, very professional highway patrol (CHP). it certainly isn't for lack of enforcement capability.
- a very large population (39M) means state politics is a combination of huge bureaucracy and big money. there's a proposition system, but even that is essentially inaccessible without lots of money. even if something good did start organically, by the time it was mangled by the self-serving politicians it'd end up worse than where it started.
- california has roads and drivers. lots and lots of both. and lots of urban sprawl too. nearly everyone has to contend with it, like it or not.
so the reason "everyone" responds to this by exceeding the limit, is that it's easier than the alternatives. a majority of the drivers "realize" (to some extent) that they have approximately three options:
a) drive the speed limit and get punished by other drivers and sometimes law enforcement [1],
b) same as a, but make it one's life mission to change the laws effectively, or
c) put your foot in it and go with the flow of the herd. even if there were 10x the CHP presence, they can't stop everyone.
there are so many people who vote this way with their accelerator pedal, that if you go with the flow of traffic even if it's 20mph over the posted limit for 10 years you might not get a ticket. if you ever do, no harm, no foul: you were simply randomly selected for the "extra road tax".
this is a different kind of democracy. it's very "direct" and very real time. the rules aren't written down, but they aren't imaginary either. in short, it's the polar opposite of the dejure government system. it's actually extremely democratic: one car, one vote for the "correct" speed.
of course there are outliers and "criminals" in this society: the guy in the black mercedes who "doesn't give a shit" and wants to go as fast as he can. his concern for the other drivers is as slalom obstacles. AND ALSO the guy who sets his speed control to whatever the sign says and becomes an obstruction. they are both ignoring the other drivers and thumbing their nose at the rules of that society.
it's a lot worse than "goofy". when you've conditioned people that the "right" way to effect change in government, whether democracy or not, is defacto closed-off and inaccessible. and then there's a problem, people will organically find a way to fix the problem. if the cheapest easiest way is simply to ignore the dejure government rules en-mass, that's what will happen. it's hard to imagine how to "get back" from it, if that's what you want. it's a testament to the unprofessionalism, selfishness, and pure stupidity of our elected officials that they've ignored this possibility allowed it to cross that line.
as for speeding, if california would post really reasonable speed limits, a larger group of people might find it "not worth it" to go faster than posted. perhaps they didn't really want to go faster in the first place. you'd have to make this a solid majority in order to cause the pirate society to fail. it doesn't seem that likely. it's pretty cheap to just ignore something.
[1] if you drive substantially slower than the "herd", perversely you will draw more CHP attention and be more likely to be pulled over. are you drunk? is your car unsafe? are you on the phone? violating CVC 24000? are you unlicensed or uninsured? are you simply the first/slowest car the motor-officer catches up to, and therefore a safer/faster option to get to the next doughnut?
but i will also emphatically reject your position: "Constructors, exceptions, and so on are as similarly visible at the source level as macro definitions"
no they are not. you can certainly see what the macro is doing - you see it's definition, not just it's existence. whereas in c++ you have to trust that language/compiler to:
- build a vtable (what exactly does this look like?)
- make copy ctors
- do exception handling.
- etc.
none of these are explicit. all of them are closed and opaque. you can't change their definition, nor add on to it.
at issue at hand is both "magic" and openness. c gives relatively few building blocks. they are simple (at least in concept). user libraries construct (or attempt to construct) more complex idioms using these building blocks. conversely c++ bakes complex features right into the language.
as you note, there are definitely forces that work against the naïve original nature of c. macros, setjmp, signal handling, instrumentation, hardening, .so resolution, compilers replacing primitive accesses, etc. but all of those apply equally to c and c++. they are also more an affect of the ABI and the platform/OS than either language. in short, those are complaints and complexities due to UNIX, POSIX, and other similar derived systems, not c or c++ the language itself.
c has relatively few abstractions: macros, functions, structured control flow, expressions, type definitions. all of these could be transformed into machine code by hand, for example in a toy implementation. sure a "good" compiler and optimizer will then mangle that into something potentially unrecognizable, but it will still nearly always work the way that the naïve understanding would. that's why when compilers do "weird" things with UB, it gets people riled up. it's NOT what we expect from c.
c++ on the other hand has, in the language itself, many more abstractions and they are all more complex. you aren't anywhere near the machine anymore and you must trust the language definition to understand what the end effect will be. how it accomplishes that? not your problem. this makes it squarely a high-level language, no different than java or python in that facet.
i explicitly reject your position that "that C is qualitatively [not] different from C++ from a WYSIWYG point of view, [either] theoretically [or] in practice."
to me, it absolutely is. it represents at lower level interface with the system and machine. c is somewhere between a high-level assembler and a mid-level language. c++ is truly high-level language. yes, compilers and os's come around and make things a little more interesting than the naïve view of c in rare cases . but c++? everything is complex - there is not even workable illusion of simplicity. to me this is unfortunate because, c++ is still burdened by visible verbosity, complexities, land-mines, and limitations due to the fact that it is probably not quite high-level enough.
this is all very long winded. you and many other readers might think i'm wrong. the reason i'm responding is not to be argumentative, but because it is that it's by no means a "settled" question and there are certainly also plenty of people that see it a very different way. which i think is fine.
- macros are also standard C++ features too, so this point doesn't differentiate between those languages
- i'm failing to adequately communicate my point. there's a fundamental difference practically and philosophically between macro stupidity and C++ doing things under-the-hood. of course a user (you, a co-developer, a library author you trusted) can do all sorts of stupid things. but it's visible and it's written in the target language - not hard-coded in the compiler.
yes - sure, good luck finding the land-mine "b" macro if it was well buried. but you can find it and when you do find it, you can see what it was doing. you can #undef it. you can write your own version that isn't screwed up, etc.
you can do none of those things for operations in c++ that occur automatically - you can't even see them except in assembly.
and yes, in fact, volunteering at a hospital should be viewed favorably for pre-med.
and yes, you will be a better student if you play some kind of team sport like softball than if you did nothing.
so perhaps the comment i was replying to made bad arguments? for example, if a school only liked mainstream athletics and ignored anything else (which is probably not a stretch), that would be a better example of "having their heads up their asses".
but the specific examples given were the opposite - they actually make sense.
- https://web.archive.org/web/20130216132858/http://www.cantri...
- https://nsjonline.com/article/2021/12/bonhoeffer-on-stupidit...
never-the-less there is still a lot of truth to the saying, nobody said it was universally categorically true.
i've written clever code when it needs to be clever, for example performance. along the lines of the RCU code. when i do i plan for handling the complexity - static analysis or exhaustive testing if possible.
suddenly needing to advance your cleverness by 2x isn't impossible, but it's not fun if your butt is on the line.
whereas you can see the user-defined macro definition of "b" at the top of the file. you can't blame the c language for someone choosing to write something like that. sure it's possible, but its your choice and responsibility if you do stupid things like this example.
Mashey was really talking about workstations, not PCs. of course, the line is blurred or non-existent now. what if we look at x86ish PCs?
presume that in 1995, a nicely appointed high-end PC was a 486DX-33 (w/487) and 16MB of ram. that requires 24 bits of physical address. using 3/2*bits per year estimate, we find that we need more than 32 bits around 1995+(3/2*(32-24)) = 2007.
AMD64 came out in 2003/4. but my own recollection is it wasn't really the sunset for 32 bit PCs until just about that timeframe (2007 ish). so that's not too far off.
now apply forward to when we "use up" 48 bits (or 52). and it would be around 2031-2037. possible?
now the other thing, is that (imho) a nicely appointed PC today in 2024 is 64GB (36 bits) vs. 16GB (24 bits) in 1995. does this track? not really. the 2 bits every 3 years would predict that we'd want 64GB machines in 2011? that's not really realistic. and it'd predict that we'd want ~16TB PCs by 2025.
it seems apparent that the exponential growth that was happening in the 1980s and 1990s has either slowed substantially or is no longer exponential for perhaps the last 20ish years.
i think the lesson (and for Moore's law too) is that apparent exponential growth is not going to continue forever.
no, that is exactly what he meant. clever code means you are just barely able to understand it enough to write it yourself [in any amount of time]. therefore, you aren't going to be able to debug it at all, by a factor of nearly two. and if you are the "smartest" person in the org (which he often was), then you are really in big trouble.
now obviously things in the real world like "smart" and "clever" are not one-dimensional quantities in neat categories, but he was making a memorable and funny quote, with quite a bit of truth to it, not a precise scientific hypothesis.
see also: "too smart for one's own good"
> nonsensical interpretation
how so?
> someone twice as smart may not be able to figure out what the stupid person is trying to do in the first place if the code written was nonsensical.
true, but irrelevant, this is about clever code from a smart person, not nonsense code from a stupid one.
> Is my kid really going to be a better student because she volunteered at a hospital[?]
as a sibling comment pointed out, certainly. because you'll know what your getting into vs. a romanticized fantasy or some salary-based-major selection.
> Is my kid really going to be a better student because she [...] played high school softball?
yes, 100% yes. of course it doesn't have to be sports, but it has to be something other than sitting on the couch. sports teaches teamwork and leadership skills. music does the same and more. other hobbies promote exploration and independent learning, and could be tied to developing interests. kids that have done stuff are going to be way better at college and life than those who never did anything outside of the limitations of public school.
- just don't take it to extremes (if one extra-curricular activity is good, 5-10 should be great!)
- just don't get focused on sports only. not everyone is an outdoor sportsman. anything should be fair game.
i don't find the "people behaving badly" video genre a classy form of entertainment, but that's all it is.
i suspect the meme status of it is especially relevant due to the global social context of this art - it may be a statement along the lines of "the best reality show is americans".
i don't totally disagree with the author. but i offer a different viewpoint:
- some "perks" fake-stock (RSUs), free food, unlimited time off, etc. are not necessarily there because of a “people first” focus. they are a subtle physiological con-game and relatively cheap to implement.
- others, the absurdly high compensation for example, are market driven. the author, imho correctly, points out reckless "hypergrowth" as a driver.
so to me there's no real contradiction, just instability. there are booms and there are busts. the less stability, the further the extremes go. theoretically in both directions. the oil/gas-field industry is another example with similar booms/busts and high compensation (on a good day). jobs like this can be great ways to make a lot of money if you can personally tolerate the downside risk (perhaps young and unattached).
i think the subtlety is that it's just a teeny bit unseemly to package these jobs as something they are not ("people first") when they are actually often cyclic market driven bets and the prospective employee is just a part of that speculative activity.
the author argues roughly that if you say people first, you should actually do that.
i'd argue, that if it isn't really, never was, and won't ever be, then they be more transparent about it. and since that won't ever happen, the best thing is to stop being deluded and see it for what it is; go in with open eyes.
is your long term economic value as a coder really 5-10x a teacher? or maybe some of it is a speculative bubble.
you just described "make" as well as cmake. let alone autotools (./configure, Makefile.am, etc.)
"It has terrible syntax, terrible semantics, and you need to run Make anyway"
agree. the core reason, overriding all of that, is that it fundamentally does a different job. Make is an engine that takes a high-level description of rules and dependencies, builds a graph of them, and then executes on it. but in order to work correctly, you need a full dependency graph.
the problem is that when you have a large project with lots and lots of directories that build a bunch of inter-dependent artifacts, you don't necessarily like having one single big monolithic "Makefile". so of course you break it up. Every directory has a fragment that describes just what it builds, and so on.
the old way of doing that was hierarchical makefiles and "recursive make" [1] which kinda works OK, but treats each leaf makefile and directory as an independent product. the core makefile only knows coarse dependency information about those directories as a single unit. this also has pretty severe performance and parallel build issues.
the right way of doing it is some kind of multi-stage makefile system. the first stage doesn't build the product, it builds a concrete monolithic makefile containing the whole dependency graph from distributed information in each part of the project. the second stage builds the product.
you can write the first stage in python, bash, gnu-make, etc. but make is really a difficult tool to write procedural type code in. the linux build system does this though, but it's certainly not simple.
so that's all CMake is (wonky syntax and all) is doing. and it's just a bespoke system tuned specifically for doing C and C-like compilation that allows you to build a makefile (or Ninja or etc. etc.) backend. of course it has all kinds of other features as well, but to me the core difference is that make is low-level and cmake fills that role for a high-level system.
also me: AI is evil because it tricks people into giving up their creativity, which isn't the boring part, it's the real part
also also me: wtf? why bring that up?
"while you sit on your ivory pedestal of superiority. Your choice."
ha! if only! i actually sit in a dim room with remnants of caffeine and pizza and wonderful half-broken computers and brand new ideas and code and interesting challenges and discoveries. and friends.
i did choose.
correctly.
it's not Luddite behavior for saying "no, we don't want to do that"
this is fundamentally different. this is a machine, a mathematical equation, that converts enormous amounts of history and facts into a facsimile of creation, thought, expression. it does it convincingly in very small doses, but it doesn't do it all that well. unless your task is to regurgitate something relatively mechanical.
a car was something new. a mechanical horse. it wasn't some distillation and averaging of every extant horse into some "perfect" mutant horse. it was genuinely new. it also wasn't a mirage or a hallucination.
AI is not a creative force, rather reductive. it's at best a tool. so if you want to copyright something or you want to contribute to NetBSD, sure, that's fine. but copy-paste of someone else? no matter what the underlying process, it's still wrong.
what happened also seems to fall much more squarely under fraud (e.g. lying to the FAA) than simple negligence. failing to notice that they missed steps or didn't complete paperwork would be negligent (which they probably have done), but existing criminal case is about intentionally lying about a design change and it's ramifications to game the certification process. that's really bad. way worse.
but this is made worse in no small part by security researchers, students, companies etc. are all using a CVE as an achievement or some kind of feather in their cap.
now, you get thousands of "CVE-2024-10340494: water is wet" and the related "CVE-2024-10340495: if users look up in the rain, they could conceivably drown". of course it would always also have a blog, a custom domain-name, a catchy title/nickname, etc.
it's Goodhart's Law in action: "when a measure becomes a target, it ceases to be a good measure."
and what else could the Linux devs reasonably do? it was either this or ignore CVE's entirely.
"other may be doing the same to you"
and they might not even be tricking you into doing the "right thing", just the thing that they want.
there's a very odd similarity between her mothers' delusion about cat 4 hurricanes and her own example of people being "blown out of their apartments by typhoon-strength winds". having disasters like that thrown in your face constantly by every conceivable media source probably doesn't help.
fwiw, other essays: "Panic. It's Good For You.", "They Want Us All To Die", etc.