|
|
I recently purchased a low end laptop for testing software. I find that the Windows 11 it came with is pretty snappy.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
The trouble is, I'm lacking inspiration, and things like Entity Framework, XML serialization (which is crap, but it's there), and other obvious applications of it have already been done to death, or are produced my microsoft, and in everybody's regular rotation such that a contribution in that arena would be at best futile, and at worst annoying.
I wrote a great lexer generator that uses it. But now what?
I've talked myself out of generating parsers. Short of some sort of AI code synthesis, they are too bloated and restrictive to be very practical in the real world.
I thought about generating component model stuff, like the common component property changed event patterns on classes but the core stuff really involves UI components, and it seems like .NET UI is still all over the place. I want the dust to settle before I commit to something like MAUI.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Probably old but new for me...
• An Oxford comma walks into a bar where it spends the evening watching the television, getting drunk, and smoking cigars.
• A dangling participle walks into a bar. Enjoying a cocktail and chatting with the bartender, the evening passes pleasantly.
• A bar was walked into by the passive voice.
• An oxymoron walked into a bar, and the silence was deafening.
• Two quotation marks walk into a “bar.”
• A malapropism walks into a bar, looking for all intensive purposes like a wolf in cheap clothing, muttering epitaphs and casting dispersions on his magnificent other, who takes him for granite.
• Hyperbole totally rips into this insane bar and absolutely destroys everything.
• A question mark walks into a bar?
• A non sequitur walks into a bar. In a strong wind, even turkeys can fly.
• Papyrus and Comic Sans walk into a bar. The bartender says, "Get out -- we don't serve your type."
• A mixed metaphor walks into a bar, seeing the handwriting on the wall but hoping to nip it in the bud.
• A comma splice walks into a bar, it has a drink and then leaves.
• Three intransitive verbs walk into a bar. They sit. They converse. They depart.
• A synonym strolls into a tavern.
• At the end of the day, a cliché walks into a bar -- fresh as a daisy, cute as a button, and sharp as a tack.
• A run-on sentence walks into a bar it starts flirting. With a cute little sentence fragment.
• Falling slowly, softly falling, the chiasmus collapses to the bar floor.
• A figure of speech literally walks into a bar and ends up getting figuratively hammered.
• An allusion walks into a bar, despite the fact that alcohol is its Achilles heel.
• The subjunctive would have walked into a bar, had it only known.
• A misplaced modifier walks into a bar owned a man with a glass eye named Ralph.
• The past, present, and future walked into a bar. It was tense.
• A dyslexic walks into a bra.
• A verb walks into a bar, sees a beautiful noun, and suggests they conjugate. The noun declines.
• A simile walks into a bar, as parched as a desert.
• A gerund and an infinitive walk into a bar, drinking to forget.
• A hyphenated word and a non-hyphenated word walk into a bar and the bartender nearly chokes on the irony.
|
|
|
|
|
 had forgotten this one. still funny and clever
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
A double-negative didn't never go into a bar.
|
|
|
|
|
A spoonerism balked into a war.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
Now THIS is the type of content we like to see!
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
If you had to pick a song that described you, what would it be? I'll kick things off with mine:
I can't help about the shape I'm in
I can't sing, I ain't pretty and my legs are thin
But don't ask me what I think of you
I might not give the answer that you want me to
Oh well
This describes me so well... I probably think this sone is about me... don't I. 
|
|
|
|
|
I believe the title is
" everyday people"
...different strokes for different folks...
|
|
|
|
|
|
Slip Slidin Away.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Would "a broken record" qualify?
|
|
|
|
|
Too old to rock and roll, too young to die.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
5teveH wrote: If you had to pick a song that described you, what would it be?
Whitesnake - Here I Go Again
(SFW, unless your boss hates life)
Jeremy Falcon
|
|
|
|
|
"A little time, a little trouble, your better day"
Badfinger, "Better Days" No Dice Album
Great guitar solo from Pete Ham
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
|
|
|
As an incredibly enthusiastic user of C++ from its very first release, I've expressed this (personal) opinion a number of times over recent years: C++ has lost its way - it now takes more time, learning, effort and skill to make good, efficient use of C++ than it takes to solve the problems one is using it for.
A caveat: I am thinking specifically of business tasks and related domains - I accept that for the most cutting edge stuff near to the metal it still offers the one of the best overall effort/performance ratios.
In part, the effort to maintain backwards compatability at almost any cost (despite the fiasco of i(o)streams and manipulators between versions 1,2 and 3) whilst adding ever more features adds huge amounts of technical debt that then has to be fought against in other ways.
This article I think demonstrates this nicely Speeding Up C++ Build Times | Figma Blog[^]
Discuss! (ducks for cover...)
|
|
|
|
|
Quote: However, there are other common solutions that we also employed to reduce build times, including local caching, remote caching, and precompiled headers.
From the rest of the writing, it seems they haven't implemented precompiled headers correctly, because all their efforts to eliminate redundant headers amount to very little savings if the precompiled header gets each precompilation unit added once and then not again with additional redeclarations. At least that is the way I understand precompiled headers, and they have saved me a bunch of time in the past. I wish they would have talked about that aspect more as my understanding could be deepened.
PS - Mike Winiberg wrote: In part, the effort to maintain backwards compatability at almost any cost (despite the fiasco of i(o)streams and manipulators between versions 1,2 and 3) whilst adding ever more features adds huge amounts of technical debt that then has to be fought against in other ways.
This article I think demonstrates this nicely Speeding Up C++ Build Times | Figma Blog[^]
I don't see that article supporting your assertion in any meaningful way. All it seems to be saying is that their coders haven't kept their headers clean, and often included unneeded headers that they had to take out. That doesn't seem to be speaking about the difficulties inherent in modern C++.
|
|
|
|
|
"I don't see that article supporting your assertion..."
Well, YMMV indeed, but it demonstrates quite nicely, I think, how - in an attempt to maintain backward compatability - the C++ environment has required ever more esoteric procedures to keep it usable both compiling the code and learning the language and its libraries etc. That one should need to have precompiled headers, write add-ons (which even google had to do) to make compilation times acceptable etc speaks very well to the increasing complexity of the whole ecosystem, in my view.
Don't get me wrong, I'm not saying it isn't a good powerful dev environment - my team developed a whole airline/shipping/freight system in C++, and financial applications using parallel C++ for market-maker using a Transputer farm. But I reached a point where I realised it was taking far longer (for us anyway) to learn how to make good use of the ever increasing new features than it was to solve the problems we were facing.
Having made extensive use of one feature (manipulators on streams) to control printing, only to have that broken - and hence needing a rewrite - in version 2, followed by a partial regression in version 3 (another rewrite!), then complete collapse of our system after a third-party database library we were using was updated and broke references (implementing them by copying FFS) we came to the conclusion we were spending more time fighting the language environment than writing software.
Switched to Java, then later to Python, and heve not used C++ in a meaningful manner since.
If there is one thing I have learnt in my altogether too-long time in software dev, it is that - with a few domain specific exceptions - the language you develop with is largely irrelevant, so the less it gets in the way of the task you want to accomplish, the more productive you can be.
|
|
|
|
|
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
I agree with you that C++ is in danger of becoming a modern version of PL/1, containg something for everyone. I also agree that learning the entire language (and standard libraries) is becoming more and more difficult. However, C++ shares with C the philosophy that "if you don't use it, you don't pay for it" (or words to that effect). There is no reason that you can't use C++ as "C with classes", or at any other level between that and C++20/23/xx.
The language features I most use are RAII (exists from the ARM), templates & exceptions (C++98), threads & atomic variables (C++11), smart pointers (C++11?), and a few more advanced features (various, up to C++17). These have changed slighly over the years, but the changes are manageable.
Obviously, I use the standard library as well, but most changes to that have not been breaking changes.
Mike Winiberg wrote: Speeding Up C++ Build Times | Figma Blog[^]
Lastly, a decent developer spends most of his/her time on designing, writing code, and thinking about the code (debugging). The compilation time should be a small fraction of the total development time, and even that (as the article points out) may be optimized with a good design of your system.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Damn, that article is making the rounds !!
The (one of) problem with C++ is that it's an old language that needs to compete with more modern languages.
It can only be incrementally improved.
We underestimate how large the C++ code base is actually in production.
You can't just break backward compatibility (as much as I would like them to do it)
If that happens, many, many large organisations will never upgrade their toolsets.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
