This is more of an artifact of needing to be compatibile with other browsers and more of an arbitrary decision where once one browser starts allowing all sorts of input than everyone else may start needing to if content starts relying on it.
>But the world is better for it.
It makes compatibility between different browsers more complicated due to adding a ton of edge cases that all need to be handled the same way as opposed to following a standardized way of writing pages.
>The user experience of XHTML was rubbish. The disrespect shown to anyone for deviating from the One True Path made it an unwelcoming and unfriendly place.
The UX could be improved along with developer tools making it harder to mess up and easy to spot mistakes. For example many internet forums have similar requirements of needing to match formatting tags and those have work successfully despite being strict. I think the real issue was that XHTML was introduced too late. Trying to fix things in a decentralized ecosystem is an extremely big uphill battle. If you don't fix things at the very start things can grow out of one's control.
>The beauty of the web as a platform is that it isn't a monoculture.
There is also beauty in that there is a standard that everyone can follow to ensure that pages written can work the same in all browsers.
>I cannot fathom how someone can look at the beautiful diversity of the web and then declare that only pure-blooded people should live in a particular city.
The way people interact with each other in the real world is very different than the way browsers render pages. I do not think such a comparison makes any sense to make.
>How do you acknowledge that the father of the computer was a homosexual, brutally bullied by the state into suicide, and then fund groups that want to deny gay people fundamental human rights?
Just because someone was in the right place at the right time does not mean that they are of perfect moral character. It's similar to the quote to never meet your heros. The people you may look up to in regards to some achievement may not be the best of character and keeping a distance from them may be the best else your opinion of them may be tarnished.
>When you throw slurs and denigrate people's pronouns, your ignorance and hatred does a disservice to history and drives away the next generation of talent.
I disagree that this happens. At best it discourages a subset of the next generation, but it is not a subset I would like to work with. These kinds of people could also drive away other potential talent too. Simply increasing the number as opposed to trying to build a positive, healthy, culture and growing it I don't think is the best idea.
>This isn't an academic argument over big-endian or little-endian.
It could be about these 2 choices. For example x86 processors were able to be extremely successful despite not being tolerant between big and little endian. By picking a single one and running with it, it's been able to help unify computing on little endian.
> >When you throw slurs and denigrate people's pronouns, your ignorance and hatred does a disservice to history and drives away the next generation of talent.
> I disagree that this happens. At best it discourages a subset of the next generation, but it is not a subset I would like to work with.
Tell me more about this subset you wouldn't like to work with.
I do not want to work with people who are obnoxious, mentally unstable, love stirring drama, self centered, controlling, etc.
These attributes can make it hard to work with others, or waste time that could have been spent actually building a good product for end users. Of course people are not robots, they have emotions and attitudes that are variable so some people will exhibit these qualities some of the time, but I believe it's important to build a culture that can withstand these rather than amplify them.
> I disagree that this happens. At best it discourages a subset of the next generation, but it is not a subset I would like to work with.
The subset most discouraged is likely those targeted by discrimination - women, minorities, gay people. Not a great look to say you'd rather not work with that subset.
I think you are being downvoted because Ethereum requires you to stake 32 Eth (about $100k), and the entry queue right now is about 9 days and the exit queue is about 20 days. So only people with enough capital can join the network and it takes quite some time to join or leave as opposed to being able to do it at any time you want.
Considering how useful I've found AI at finding and fixing bugs proportional to the effort I put in, I question your claim that it's being underfunded. While I have learned things like Idris, in the end I never was able to practically use them to reduce bugs in the software I was writing unlike AI. It's possible that the funding towards these types of languages is actually distracting people from more practical solutions which could actually mean that it is overfunded in regards to program verification.
>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software.
Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l
of days from receiving the patches to having a validated OS release with the fix being sent to users. It's not the control of Android which makes Google possible to patch their Pixel branch of AOSP faster than Samsung can patch their own. It's that Samsung doesn't care about prompt security fixes so they don't allocate engineers to do the work.
If you want to go that route, each manufacturer is responsible for their own drivers for windows, linux, and possibly Mac (though if it’s novel enough, they will do it). Then think about the components that make up a PC. Motherboard, CPU, Memory Control, IO, OS, Audio, Video. Each of those needs to release patches. So its orders of magnitude more than any Android OS. It’s just pure laziness on the hardware manufacturers that don’t want to invest in software/support. They want Google to do that.
The big difference with PC hardware is that the OS will get most driver updates for the individual components directly from the OEM. A driver update for, say, a sound card will directly be available to every machine with that sound card installed. The PC vendor doesn't have to be involved in any way.
It's the other way around with Android. Google does a new core release, and each individual manufacturer is responsible for modifying it for their devices. If you don't bother to upstream your drivers to mainline Linux and use a skin which heavily modifies core Android, backporting those fixes can quickly become a nightmare.
Again, no sympathy as that’s the route they chose. Rely on Google for everything OS and make a phone whereas Apple made a phone and supplied an OS.
Apple made a product. Google made a software revenue stream. Entirely different things and now the Android makers are crying foul that they too have to do product engineering support. Nah. This is what you get when you rely on out of house innovation. I hope they all close shop. Not because I like Apple, but because they aren’t in the business of making products, only selling you hardware with bolt on software that it vaguely supports. Like buying a raspberry pi that can make phone calls. Google has them all by the balls.
Yeah, and I also hope that all the PC makers close up shop as well. They rely on Microsoft for everything OS. Listen, you can just enjoy your iPhone in peace. Let other people make things, even if you feel they don't meet your standards.
No, I use Android and the security nightmare on Android is absolutely unacceptable. There is zero reason phones should rely on as many proprietary bullshit blobs as they do, and that's the root cause of this.
Even just looking past the bugs that almost certainly exist in the firmware, it makes these devices extremely difficult to update. Whereas on desktop, I get kernel patches expeditiously. Many Android devices are still running kernel 5, and of the ones running recent kernels, we're still waiting months for system patches.
If everyone just upstreamed their shit, then we would live in a Utopia.
They don’t rely on Microsoft, quite the contrary. The OEM/ISV vendor relationship at Microsoft is the backbone of the company. Linux, servers, phones, infotainment, TV’s, robotics, all run a flavor of Unix (Linux being the primary, but BSD is in there).
For the consumer PC market, Microsoft cornered the market early on with IBM and HP with DOS. They then tried to pull the ladder and raise the gates when they went against OS/2 and Amiga. To win the Windows for Networks wars.
The only reason why majority of consumers use windows is because that’s how they want it. You can easily build a PC, no Microsoft Windows anywhere in a 1 km radius, and install Linux or BSD flavor of choice and be 90% there. Companies don’t want you to do that (i.e. Microsoft and Apple) so they preinstall the OS and it updates over the Internet whenever it wants to. Installing whatever it wants to. User choice be damned.
No, Pc’s don’t need Microsoft anymore than Rap needs p.diddy
Weird how LineageOS supports ~300 devices while still managing to release patches.
I bet this CVE's patched quicker on a samsung device running LineageOS than the stock OS.
The real difference is that Google has a more competent software development process and release process than other android OEMs, regardless of how many different devices they have.
LineageOS doesn't customize the hell out of their OSes per device.
That's core of the issue. Samsung takes Android, customizes per device and then tosses them into the world. So now they don't have 1 OS to update, they have 100s of OSes to update.
That's still one OS. Customization is mostly userspace "system" apps that they swap out and maintain, but reused across all their phones with some small variation. Hardware enablement will differ between models, but that's just the cost of doing business.
Can be a pain to move the whole suite to a new major (porting all their inhouse apps, getting all the hardware enablement from vendors updated to match, ...), but we're not dealing with a major upgrade here.
A security patch is "just" a matter of taking the last release, applying the diff, build, qa, release. No customization.
And 5000+ laptop models per year, yet linux runs on (pretty much) all of them. This is an entirely self-inflicted problem. They don't deserve an ounce of mercy.
Technically there is no such thing as a bitcoin. Just unspent transaction outputs. Those get spent as an input of a transaction and then are gone forever. There is no concept of the output of a transaction being the same "bitcoin" as what comes from the input of the transaction. This means if you had 2 inputs and 2 outputs of the same amount there is no way to trace which input became which output. At best you can find which outputs potentially came from an input.
When blocks are verified it just needs to validate that sum of the outputs isn't more than the sum of the inputs. It doesn't care about tracking what went where.
Except I can literally pull up a full node and see a wallets current balance - which is because it traces all the transactions through the blockchain, verifying all of them.
Literally the only way anyone can see their wallet balance is by doing this.
I will say it again. When validating the chain all it cares about is that the sum of the output UTXO for a transaction are <= the sum of the input UTXO. All the input UTXO are no longer valid once spent and can be forgotten.
Most states still haven't created digital versions of these hard-to-copy tokens meaning that there needs to be an alternate provided by a 3rd party which is where cryptocurrency comes in.
The Fed has had a wire service (Fedwire) for banks, allowing them to transfer their balances on the Fed’s balance sheet to another bank during settlement, since before the dollar moved off the gold standard. It was initially done with literal telegraphs - not sure at what point it became digital.
It obviously has no pseudo anonymity, is literally the least democratized banking system in existence, and is subject to the government’s whims in a whole host of ways. But it is a digital ledger of massive sums of real dollars (the banks can ask for it in cash if need be), and you couldn’t really steal the money even if you managed to create an unauthorized transfer on some bank’s master account.
So why don't any businesses let me Fedwire them money? It turns out unlike the physical version of cash, this "digital version" has hefty transaction fees and a poor UI meaning no business will take it, unlike how almost all physical businesses will take cash.
That’s not a technical problem - this kind of system can scale out just fine and has in other jurisdictions. SEPA is far from perfect, but is better than Bitcoin for everything but evading governments (justified or otherwise). We’ll see what Fednow looks like in a few years - the banks are definitely dragging their feet and it’s hard to tell what the
UX will look like in the end.
They couldn’t get their whole balance in cash I’m sure. But the Fed is the one that handles retiring old paper currency and giving banks fresh currency to give to ATMs and tellers, and I doubt the inflows and outflows are perfectly even for each bank.
I think we’re talking about bank reserves, which is a fraction (in the order of 1%) of the total amount of money held in the customers’ transaction accounts. Reserves are convertible into cash. Not that any bank would suddenly want to do that, unless there’s a bank run, in which case it’s the customers who want the entirety of their accounts (100x the reserves) converted into cash, which is impossible not because the fed refuses to convert the money, but because the bank doesn’t have enough reserves.
The Fed manages printed currency - they’d be irritated, but they literally do provide the physical dollars people need now, and if they felt it was appropriate, they’d produce them as needed.
Just like those airplanes of bills shipped to Iraq, etc. in the past.
To be fair, this is because the US figured this stuff out way earlier through credit cards, and now there's a bunch of stakeholders and legacy changes which get in the way of making the services better.
Indeed, and there are some good reasons, too: US regulators want to prop up smaller regional banks and avoid large national monopolies (for what is essentially a natural monopoly).
The externalities of the crappy US banking system are so vast though. Musk, crypto, ...
Inside the same country, really? We have the aptly-named Faster Payments in the UK and it's instant. The company I work for is virtually built upon it.
SEPA is among the most stable & robust payment areas globally with a lot of interesting features which a lot of other regions are jealous about :-)
And there are additional layers built on top, so at least we have N=1, while I have to admit that convenience could & should be improved
The states (or rather the national banks of said states) are usually the ones running the central clearing system. That's the place where all the different banks report their net change in relation to all the other banks, and settle that change on their account with the central bank.
Believe it or not, banks don't ferry around cash to each other. It's all just numbers in a computer.
So does being able to download a new version of software that uses different memory addresses. The point is if you are able to patch software, you are able to patch memory maps.
This is more of an artifact of needing to be compatibile with other browsers and more of an arbitrary decision where once one browser starts allowing all sorts of input than everyone else may start needing to if content starts relying on it.
>But the world is better for it.
It makes compatibility between different browsers more complicated due to adding a ton of edge cases that all need to be handled the same way as opposed to following a standardized way of writing pages.
>The user experience of XHTML was rubbish. The disrespect shown to anyone for deviating from the One True Path made it an unwelcoming and unfriendly place.
The UX could be improved along with developer tools making it harder to mess up and easy to spot mistakes. For example many internet forums have similar requirements of needing to match formatting tags and those have work successfully despite being strict. I think the real issue was that XHTML was introduced too late. Trying to fix things in a decentralized ecosystem is an extremely big uphill battle. If you don't fix things at the very start things can grow out of one's control.
>The beauty of the web as a platform is that it isn't a monoculture.
There is also beauty in that there is a standard that everyone can follow to ensure that pages written can work the same in all browsers.
>I cannot fathom how someone can look at the beautiful diversity of the web and then declare that only pure-blooded people should live in a particular city.
The way people interact with each other in the real world is very different than the way browsers render pages. I do not think such a comparison makes any sense to make.
>How do you acknowledge that the father of the computer was a homosexual, brutally bullied by the state into suicide, and then fund groups that want to deny gay people fundamental human rights?
Just because someone was in the right place at the right time does not mean that they are of perfect moral character. It's similar to the quote to never meet your heros. The people you may look up to in regards to some achievement may not be the best of character and keeping a distance from them may be the best else your opinion of them may be tarnished.
>When you throw slurs and denigrate people's pronouns, your ignorance and hatred does a disservice to history and drives away the next generation of talent.
I disagree that this happens. At best it discourages a subset of the next generation, but it is not a subset I would like to work with. These kinds of people could also drive away other potential talent too. Simply increasing the number as opposed to trying to build a positive, healthy, culture and growing it I don't think is the best idea.
>This isn't an academic argument over big-endian or little-endian.
It could be about these 2 choices. For example x86 processors were able to be extremely successful despite not being tolerant between big and little endian. By picking a single one and running with it, it's been able to help unify computing on little endian.
reply