So you're saying that it is impossible for a large company to somehow use native toolkits to draw text bubbles and emojis?? Video and audio is another matter, but MSN Messenger managed 75% of this decades ago, natively.
So you're saying that it is impossible for a large company to somehow use native toolkits to draw text bubbles and emojis?? Video and audio is another matter, but MSN Messenger managed 75% of this decades ago, natively.
One weird thing about software development is that there are plenty of things which motivated individual developers can achieve which large companies can't even write the requirements for, let alone achieve.
But seriously folks, this is why there will always be room for startups.
Megacorps are slow lumbering beats that suffer from entropy and signal loss at every edge on the graph.
The example here is that some marketing function gets the signal from Zuck to put Lego duplo characters everywhere because metaverse. Of course 90% of the company knows its dead on arrival so they are going to drag feet and try to work on their actual problems (or their local feifdom mandate) and wait for the latest fad to blow over.
Super wasteful, super inefficient but hey ads make an insane amount of money so Zuck can do whatever for a loooong time.
This is why Warren Buffet advocated dividends. Companies and people have few good ideas. Management however uses this money from the good ideas to fund boondoghles (see metaverse). The thinking here is that the money would be better utilized returned to investors to fund other good ideas.
That's because he comes from a generation who has "the government and universities take care of R&D" as a mindset. A lot of the stuff we take for granted today - *nix, TCP, IP, the Internet itself, lasers, microwave, radar - came out of universities, government grants or the military.
The idea that the government is incapable of R&D is relatively new and originates in small-state / lean-state / starve-the-beast ideology.
And personally, I rather believe the wisdom of an old man who made a metric shitload of money by being a good honest citizen than others who got rich on advertising and stonk market shenanigans.
So what, NASA spent billions on the new space race, with everyone knowing the true aim was to kick Boeing's ass and Boeing being widely known as a pork distributor first and foremost and rocket/plane manufacturer second.
The job of politicians isn't to cater to the whims of reactionaries, the job of politicians is to do the right thing and sell it to the voter base.
I'm not sure we should be critical of risk taking in large companies because there was some notable failures. But maybe it is the sort of thing that doesn't scale well in a large org, they want big immediately.
True. I work for one and its terrible. My work is 95% jumping through hoops imposed by other teams, restrictions put in for political reasons by substandard business 'leaders', and often even keeping vendors happy (really why should we care, we are their customers not the other way around :( )
5% is doing actual improvement. And meanwhile HR want me to show I'm making a difference to the company. Well yeah 5%.
I hate it a lot but the pay is good and a permanent contract with 20 years service is valuable (if I'd get made redundant I'd get more than a year's severance so I'm definitely not leaving on my own for something that may not work out)
We can say that for the majority of companies with large teams that already have this. Everyone knows Meta is no different.
In this case, it's a skill issue to ship low quality software which is what whoever that team at Meta just did and knowingly approved.
> The engineers at Meta are world class but they're nerfed by organizational constraints.
That doesn't mean anything given that shipping regressions to billions of users is not of "world class" calibre.
If fact, that is of amateurs behaviour and way below the expectation of a multi-trillion dollar company hiring the "best" engineers which they can certainly afford.
I'm not defending any large company, they could if they wanted to, they just don't care. If this is "cheaper" and they can cut costs, this is what they'll do.
They know web, they can manage web - web is “less risky.”
In my experience, in a large software company [0] it's very common for new folks on a "team" to have to spend one or (often) more months learning both the software they're now working on and the various libraries used in its construction.
It's very nice if you can find an expert in everything you've used on a software project, but that's not going to happen often. [1] And -IMO- if whoever you've hired can't generally come up to speed on WxWidgets in a couple of weeks while also becoming familiar with the rest of the project they're now responsible for, they're not someone you want working on your project.
[0] Which is the sort of company we're talking about right now.
[1] In part because companies generally don't want to pay enough to hire such people.
In my manual labor occupation the office folk often try to get away with a horribly inefficient schedule designed to make their job easy. I often have to remind them that they work for me. I do the actual work, your job is to optimize it.
This to me is the same thing as replacing a rather decent desktop client with a web wrapper. This is their update, its obviously bad for the customer. The excuse is to make further updates easier. There is reason to think these will also be bad for the customer.
Someone once explained to me that the process of everything we build and create is very similar. If some young sector has a wildly different approach one should be very skeptical. It happens that an architect still has work to do after delivering the drawings. Sometimes it is necessary to recall thousands of cars.
Ideal would be to have a perfect construction drawing then build the machine. The architect moves on and designs the next garden. A plumber puts the pipes in, tests if everything works then goes to the next construction site. The difference with software is that, when done, it can last forever. The opposite of what the industry pretends to be true.
I think what he is saying that native platform apps get delegated to different teams and coordinating among those teams becomes an additional cost. You don't want each team going off and doing their own thing.
Your 'answer' is "use a cross-platform GUI toolkit" but that has its own challenges. Not least that you typically build a native app because it delivers a native experience that users expect.
In general (and I accept there may be counter-examples) cross-platform tools fail to do this.
The issue is not that a native Windows app needs to run in a browser.
The issue is that a native Windows app has been replaced by yet another browser.
That's not really native either. Whether it's a web wrapper or Electron or wxWidgets, just because something runs "natively" doesn't mean it feels native.