Well. Upper tenth is just one in ten. Chances are blazing insights in that region are going to be ideas that have been had and discarded by a near a billion other people.
Whatever percentile the intellect, blazing insights are likely to be high variance ideas because they exist at the edge of the thinkers capacity. The implication is that most insights are wrong or poorly understood, as such they will be hard to explain.
It is the things that you take for granted that you truly understand and can explain, you'll just be surprised at the need. But to someone else who has less a gift for abstraction your explanation will seem a profound insight.
Well, there is still room for "learn to code" it just no longer equates to "write some JavaScript or python" there are still serious problems to solve but you won't be able to do it using preexisting libraries in languages that have nothing to do with the hardware, or do it while working for preexisting companies.
We need a new breed of computer scientists, engineers, and programmers, to write Nostr like things, that surpass the real-world utility of the current computing paradigm.
Yeah, but mostly I was the one who disappeared. It has to do with where females could be found.
My family is a melting pot of English, Scottish, Irish, French, and German. The strongest cultural influence is English though. Grew up in a Polish settlement in northern Michigan, then moved to Scandinavian Minnesota and married a German descent. We are kind of lost. Need to move back to Michigan. My old parish now resembles traditional German more than anything else. The priest does Latin masses and borrows stuff from that part of the world.
The bones are still Polish though.
If we we are going to argue units then I like to put in a word for Kelvin.
It's an absolute unit
I'll just show myself out.
My formative years were spent steeped in Polish Immigrant farming culture. My classmates were all Witkowskis, Winewetkis, Kelenskis, Popas, Plevas, Dzeleskis, Mikowskis, and Berzinskis along with a smattering of French and German lastnames from neighboring settlements that were accepted because they married in.
Then there a bunch of Wigtons that they had no choice to accept because my parents moved in with a boatload of kids and took over.
Sadly it's all diluted now and the old folks that taught us Polish Christmas Carols have died and their kids largely moved away. Some families are still there but not sure any still speak Polish.
I had a summer job 25 years ago where I was required to under go polar-shift training. The plan was that if it ever happened they would all run to the boss's parent lake house, which was a couple hundred meters from the shop, and jump on their pontoon boat. The training consisted of a lot more basking in the sun anchored to a sandbar and drinking beer than you might suppose.
That is awesome. I am still try to figure out some advent traditions for my family. I can't quite do the put up the tree the day after Halloween thing. Might put it up undecorated this weekend.
You tried. These things come up. I am sure your famous peanut brittle will be sorely missed. I only regret that I won't be able to share my candied jalapeno fruit cake.
Will you be able to attend the #parentstr meetup Christmas eve? I myself can't make it, but it should be even better. The RCMP might even make an appearance.
I think #parentstr needs it more. The only criteria is being too busy or too poor to attend even if it was nextdoor. So I am going to go ahead and schedule it for 8:00 PM (bedtime) Dec 24th in Oxford House Manitoba.
We can all not be able to make it together. Post your regrets in the replies.
Yay vbscript! Fun fact. The first production programming thing I did was as an soldering technician when I couldn't find engineering jobs out of college. They had me doing a tedious component testing process that took all week, the majority of time being spent on data entry. I decided to automate it, but they wouldn't let me install a c++ compiler on my workstation. So I proto-typed the whole thing in Excel using vbscript. Saved them three days of labor every time a new batch of sensors came in.
Didn't take long before they bought me a visual studio license, but accidentally got me c# instead of c++. And that, boys and girls, is how I learned c#.
Luckily I dodged the flash bullet. When I got my first programming job in 2010 and was still full of imposter syndrome trying to pick up the previous devs Ruby projects (also hate) my bosses wanted a second dev and asked my to talk to a candidate they really liked. He had a master's degree in cs and I was just self-taught. Guy only knew flash that was it. Just starting out after college and he had a master's degree in flash development.
I wrote a very long heartfelt email to my bosses saying that I would basically hate working with him and that flash was such a stupid technology that it would probably die in a few years. How wrong I was. Apple killed it a month later by dropping support on iOS and Safari. I often wonder what happened to that poor candidate and if he could get the money back that he paid for his degree.
Yeah not sure about that one. Too many tech stacks is a problem but a worse problem is too few. I have a bad tendency to get very judgemental of developers who want to do everything forever in the first language they ever encountered. "Look ma I hacked together some little JavaScript thing and now I insist that serious backends also be written in js." Or python people sticking with it long after their project has scaled out of making sense in python. "We'll throw hardware at it!"
My all-time most hated language I've been forced to deal with is coldfusion, brought to you by the people who's first "language" was html.
If rust can have an "unsafe" keyword to allow poking at memory when nothing else will do the languages can introduce a 'sudo give me access to your private members' keyword.
I'll enthusiastically agree with the hidden internals thing. I sarcastically LOVE writing wrapper classes for your library because you decided I don't deserve insight into critical internal state.
The handholding in rust doesn't come from mut or not. It is from the borrow checker. That is a completely orthogonal language choice to mut by default vs const by default.
I will admit I hate lifetimes and am annoyed that I can't have shared references without making them reference counted. That is where I struggle and time is wasted.
The biggest problem with rust is that while I am trying to make sure I code in a rust approved way, you are off getting things done. Maybe if I had more than a hour to code a week I'd get proficient enough to no longer be slogging through all the time.
The benefit of rust is that once you get it to compile you will absolutely be rewarded with better binaries. Can c give you binaries on par with or better than rust? In theory yes. In practice no. Even the best programmers make the kind of mistakes that rust prevents. Languages like go cannot create binaries on par even in theory. There will always need to be runtime checks for garbage collection.
The question I would pose to you boss is what problem is she trying to solve in switching to rust. If you need better binaries then go for it. If you need faster development then why are you even thinking about it instead of coding?
yes, immutable by default is dumb and forces you to do a lot more running around with the GC
that's the biggest mistake in Go, but only affects strings, in Rust it's everything
the adoption of this idiotic notion was the reason why i immediately did not want to try V either, and nostr:npub16c2fsg7fp3yxte9ugd9yhcdpa68h924asv5d6pvm5nc37a3nkzmqd2xaj2 made a language similar to V which also has this idiotic notion in it, unless i'm mistaken
wrong, wrong, wrong
this is why the only programmers who aren't gophers that i respect on nostr are C programmers, because in C you have to do things the same way, mutable by default for everything including strings
Hard disagree. Have you seen c++ code with const everywhere?
Also it has absolutely nothing to do with the garbage collector as you call it. Either a value is mutable or it is not. The declaration is strictly for the benefit of the programmer. I am old enough to remember John Carmack wishing he had const by default in c++.
The garbage collector in rust is merely a compile-time check to see if a value is out of scope. If so it inserts a free. This means you absolutely are not going to run into the same issues as a normal garbage collected language. There is no runtime garbage collector.
Oh I see you addressed that below in the thread.
Just to be clear. In rust everything is immutable be default. The flag is `mut` to make things mutable. So same thing really but making it the inverse vastly cuts down on how often you need to type it in.