Sure, you can run a 20 year old app, but that is not the same as a current app still working in 20 years, or even 5.
9,034 karma · joined January 12, 2017
Sure, you can run a 20 year old app, but that is not the same as a current app still working in 20 years, or even 5.
Then you are comparing "bank account interest and debt systems" to "embedded drivers".
Or "tax systems" to "embedded drivers".
Or "insurance policy engines" to "embedded drivers", etc.
COBOL is not a use-case, and all of the above could be done in any language. If we are discussing the qualities, ease of training , workforce availability and overall viability of COBOL, it is against the qualities, ease of training, workforce availability and overall viability of other languages.
> We can train up COBOL developers MORE easily than embedded driver devs.
And we can train up web devs more easily than embedded driver devs.
Your argument makes no sense, as it is a false dichotomy. It also entirely misses the point that I stated earlier, that a company does not want to be able to train developers, they already trained developers to be in abundance in the market.
> I've know embedded driver developers and y you're completely wrong
I work in embedded (nowadays audio and display tech), and with driver development (to make said embedded devices useful, previously for high performance datacenter network equipment), and you're completely wrong.
Not to mention delusional regarding COBOL to the point of being a suspect of IBM employment. The only still relevant quality of COBOL is that it does not self combust so we can take our time with replacing it with something contemporary and financially sensible.
You are making a false comparison. Even if we assume the number is correct, you're making a false comparison - COBOL is a language, "embedded drivers" is a software component. The equivalent to your COBOL number is all C/C++ developers.
Looking at some random online statistics like you did, COBOL is at 0.7% usage in 2024 vs. 20.3% for C and 23% for C++. Is that statistic credible? No, but neither is yours, and what matters is that COBOL doesn't.
Compare language or language, or component to component.
(Not to mention that "embedded driver developer" is not s category I'd ever make - half of what an embedded developer does would be classified as "drivers", and that term is only really used for non-embedded.)
That workforce is a small retiree club at this point, with financial institutions panicking and trying to promote COBOL and push it into computer science programs.
"Steadily deliver" is not a quality you can blanket assign to a group of people, and sounds more like an excuse for poor performance. The only quality one can assign to a small group of people will be lack of competition, which is purely about numbers, although that itself does not mean there won't be good developers in the group - just that that there is a lack of stimuli to grow the baseline.
Using a language with no real community support and a very small available skilled workforce has massive negative effects on cost and productivity (i.e., the ability to deliver changes at reasonable cost, in reasonable timeframes, and with reasonable success).
You don't want to have something that people could be taught to operate, you want something where skill is a commodity and competition is sprawling. COBOL fails on these parameters, and therefore it is "legacy and bad".
You can replace COBOL in the above with any language having insufficient contemporary adoption.
Within the EU definition, VAT taxes the company making the sale for the increase in value of a product through the processes the companies and distributors applied to it, and is not a taxation of the receipt of said value.
There is nothing illegitimate about then consuming the product in a different country. It just doesn't happen to send money to your own country's treasury.
The reason regular salaried employees do this less, limited to the kind of sort arbejde ("under the table" labor) you describe is because it has become obscenely difficult to do anything meaningful with sorte penge (untaxed money) - not because people don't want to do more or didn't previously do it.
Denmark does its very best to make it either a pain in the arse or impossible to use company property in any way that could be seen as having private value. Did you drive home in your company car? Then get ready to be privately taxed of its full market value and for the company to get a bill for the VAT. Did you take a private phone call on a company phone? Then you have to pay the "free phone" tax and the company VAT of the phone. Did you buy furniture for your home office, but without having the home office locked to physically separate it from your regular home, or did you put a comfortable chair in there so it its private value becomes ambiguous? Not a valid company purchase.
Weird US tricks like getting paid in stock and taking loans with that stock as collateral, with the resulting liability cancelling out remaining tax also don't work there. The common stuff would be, say, restaurant owners inexplicably having really low private food expenditure, or really low revenue on paper for how popular the place is.
I suspect the reason is that the US government has pressure from lobbyists to maintain the status quo, while the DK government has pressure to claw in taxes to cover their sky high spending ambitions.
Unlike what this article suggests, tax fraud is also relatively common (one would have to be rather daft to assume that a country with such absurdly high taxation did not have tax evasion as a key pastime - although probably not as aggressively as in places like the US), and while heavily frowned upon certainly not seen as the highest form of crime as this article suggests. Well, maybe if you ask the tax agency and the political parties pushing for ever more welfare, both of which push heavily for a cashless society where all financial transactions are fully trackable by them, but I think most would place tax evasion quite far down on the list of significant crimes.
I would instead say that the average Dane is carefree about these issues, not because they are trusting or believe their system is worth religious following, but because the issues experienced there feels quite minor compared to what seems to happen elsewhere in the world. When your concept of a significant natural disaster is a flooded basement, you tend to not worry that much about what happens locally.
Also, a very significant portion of drivers overestimate their driving skills, in particular older drivers. Having only been scared once in 20 years would likely make someone lenient and dull their senses as nothing requiring notable effort or attention ever seems to happen to them.
Out eyes, ears, voice and hands are quite useless when operated consciously.
That's also an issue with humans though. I'd argue that traffic usually appears to flow because most of the drivers have taken a specific route daily for ages - i.e., they are not in a novel environment.
When someone drives a route for the first time, they'll be confused, do last-minute lane changes, slow down to try to make a turn, slow down more than others because because they're not 100% clear where they're supposed to go, might line up for and almost do illegal turns, might try to park in impossible places, etc.
Even when someone has driven a route a handful of times they won't know and be ready for the problem spots and where people might surprise they, they'll just know the overall direction.
(And when it is finally carved in their bones to the point where they're placing themselves perfectly in traffic according to the traffic flow and anticipating all the usual choke points and hazards, they'll get lenient.)
LE Audio is great though - and is already, as "the full stack" has had support for quite a while... Assuming you don't happen to get your equipment from a certain fruit supplier that is notoriously slow at implementing open standards, almost as if they want to not give you a choice outside buying their own proprietary solutions...
AirPods of various versions is common, as is many other buds. Enterprise headsets like those from EPOS (the old Sennheiser Communication) and Jabra (with or without boom) and speakerphones are common in corporate settings, casual headsets (e.g., Sony, Bose) and wired gaming headsets are common at home.
It's called sidetone. Headsets do it so your ears don't feel clogged and to avoid subconscious yelling.
Some headsets let you adjust it either through a regular Sidetone volume control or some dedicated app. Soundcards also often have this feature in the form of a Mic output volume control, done in hardware to reduce latency.
A significant difference in headset quality is in sidetone latency. The heavier the DSP processing required to get a reasonable mic output, the harder it is to hit latency targets. Headset SoCs have dedicated hardware for this - a user-space solution like Apple pulls on their laptops would not be able to meet a usable latency target.
> Another benefit is not paying the '90s GSM handsfree BT profile codec pain
LE Audio includes the LC3 codec, solving this once and for all.
In the meantime while this rolls out, various alternate codecs exist that are fairly widely supported. This is especially true when using fancier headsets with a dedicated bluetooth dongle as they have more flexibility when it comes to codecs and compatibility.
A trace at the circumference of the PCB, or a wire antenna that only take up space for the solder joint would do.
Micro-benchmarks would be testing e.g. a single library function or syscall rather than the whole application. This is the whole application, just not one you might care that much for the performance of.
Other applications will of course see different results, but stuff like enabling LTO, tuning THP and picking a suitable allocator are good, universal recommendations.
No one counts the path being changed, just like they also don't count the commit message, committer and author name/email, etc.
Having a desktop CPU with integrated 64-128GB of RAM would probably justify the lack of "upgradability" with sheer performance and power improvements. There was never much upgradability there anyway - you could start by underspec'ing and then later fill it up to the (surprisingly not that high) limit, but what you saved by not buying all the RAM up front is probably less than the extra cost for supporting it at all. Paying more than the cost of RAM to have the flexibility of not buying RAM.
(Phones have 24GB of RAM nowadays, a PC should not have any less than 64GB of RAM as base tier.)
CPU's and GPU's reclock extremely fast to my knowledge, but what we're talking about isn't dynamic reclocking, just limiting the max clock as suitable to the system design.
We already see this when we have laptop silicon that run faster clocks when using soldered RAM compared to when the same silicon is using socketed counterparts.
That this wasn't an option probably mean that they're either far too close to the limit, or unwilling to allow a design that runs below max speed.
Higher voltages improve transmission efficiency, in particularly for connectors, as long as sufficient insulation is easy to maintain. Datacenters are looking at 48V for a reason.
Nothing comes for free though, and it makes for slightly more work for the various buck converters.
> God no. USB-C connectors are fragile as all hell and easy to mishandle. I hate those stupid little almost-a-wafer blades.
They are numerous orders of magnitude more rugged than any internal connector you've used - most of them are only designed to handle insertion a handful of times (sometime connectors even only work once!), vs. ten thousand times for the USB-C connector. In that sense, a locking USB-C connector would be quite superior.
... on that single metric. It would be ridiculously overcomplicated, driving up part costs when a trivial and stupidly cheap connector can do the job sufficiently. Having to run off 48V to push 240W and have no further power budget at all also increase complexity, cost and add limitations.
USB-C is meant for end-user things where everything has to be crammed into the same, tiny connector, where it does great.
CAMM is touted as being better than DIMMs when it comes to signal integrity and possible speed. Soldered of course beat any socket, in-package beats any soldered RAM, and on-die beat any external component.
That AMD Strix Halo is unable to maintain signal integrity for any socketed RAM is a Strix Halo problem, not a socket problem. They probably backed themselves a bit into a corner with other parts of the design sacrifying tolerances on the memory side, and it's a lot easier to push motherboard design requirements than redoing a chip.
If this wasn't a Strix Halo issue, then they would have been able to run with socketed memory with a lower memory clock. All CPUs, this one included, has variable memory clocks that could be utilized and perform memory training as even the PCB traces to the chip cause significant signal degradation.
Coming in with a prepared and easy reproduction and a filed issue makes quite a difference in the response you'll get.
(For the record, I don't experience anything matching what they describe on master right now, but the post was more about PaperWM vs. tiling UX so that doesn't matter that much.)
sway 1.10 is from october, 1.10.1 is a bugfix from late january. Since they're talking about git bisect, I imagine they might be running master (i.e., bleeding edge) instead of stable releases...
Local circulation and tax payment does make a big and positive difference for many things (e.g., less transport for physical goods). Doesn't require the first recipient to be aligned with your values to have an effect.
It's just unfortunate that it had to be forced for stupid reasons, especially as it doesn't necessarily make sense for everything. This timeline sucks.
If you need to add human readable information (which is your scenario), a URL is never the right answer. Write a name or a sentence. Computer-readable information is for computers to read.