Why cant I call column 1's width "x" and ask the renderer to make column 2's width "3x"? Or use these parameters across tables, so that the columns in table 1, table 2 and table 3 are all the same size?
Reworking the rendering engine to do that takes time and money. If web browser developers are going to spend any effort doing something, it'll be to remove features we've been using happily for 15 years, enhancing the user experience with more telemetry, "brand awareness", or fishing for excuse why nobody needs vertical tabs.
To be fair, I used to work in a warehouse where almost everyone was broke, but the parking lot was filled with big-assed SUVs. One of my co-workers kept bragging about how he was going to buy a used Lexus, because he always wanted one. It was real hard to explain to him that replacing a shock absorber on one of those cost as much as a decent used economy car. Obligatory car analogies are so useful because the damn things are so expensive and a good indicator of one's financial responsibility.
Don't even get me started on the flurry of brand new iPhones, being used constantly on the job by people operating dangerous 8-ton machinery.
If the subscription model is optional, then that's fine, but I'm worried it will become mandatory. There's no reason why I should keep paying for my small selection of games forever because people like you keep buying tons of crap that isn't good enough to play more than once.
Or Americans expecting to work less, produce less but get paid more than the other 80% of humanity forever.
Yeah, go ahead and say that to the face of somebody working 2 jobs, 60+ hours a week, and is still broke.
I'm pretty sure that my rent and other basic costs are much higher than the rest of the world. Owning a car is pretty much a necessity in our society. We get nothing for our taxes but more potholes, and we have the gall to charge tax penalties for not buying insurance from private companies.
My dad's Ford has an electronic parking brake, and I still have no idea how to release it. When I borrow his car, I just never use the parking brake. The car also has automatic headlights, and I can't figure out how to turn them on permanently while driving through a tunnel (there's about a ten second delay when the lights are on full auto). Don't even get me started on the radio, with its confusing, built-in media center.
One of the biggest reasons why I own a Subaru WRX is because it's one of the exceedingly few sport cars on the road with tons of manual controls, including a manual transmission. Subaru is known for resisting the trend of too much needless electronics, and their cars sell very well. I wish more cars were that simple and honest. My only complaint is the automatic climate control, which forces me to manually turn off the A/C every single time I turn on the blower.
Then encrypt your backups yourself using your own tools, and THEN put them in the cloud. If your backups are local, you can do what you like with them.
Indeed. I can say a lot of bad things about Firefox, but it never crashes on me. Ever.
I did switch to Pale Moon about 2 years ago, because it's just as stable but way faster. I use Firefox mostly for "broken" web sites that are designed only to work with popular, name-brand browsers.
How can users report bugs? There's a mantra that every developer should hide problems, either to save face or because errors are super scary looking.
I almost never get error codes of any sort these days. More and more log files are in binary format and need special tools to read. When there's a bug in the code of a web page, often all I get is a blank screen. Even the classic BSOD now has an emoticon as its primary message.
The cabinets shown in the patent illustration look almost exactly like those used in AmigaDOS v1.x. They even open the same way. The Amiga was released in 1985, and the patent was filed in 1999.
For a supposed bunch of tech enthusiasts, I see the most technophobia on this site. It's really quite pathetic.
Every day that goes by, I see another company locking us out of our products for our own protection, and taking them away from us by force whenever they want.
The electronic equivalent of book burning most definitely scares me. The only thing that's pathetic is that most technophiles I've come across never studied history and just don't give a damn.
In my attempts to track down why Firefox has huge memory problems but Pale Moon v26 does not (and Pale Moon v27 does), I've determined that bad caching policy is responsible for memory consumption, not leaks.
Firefox will cache the hell out of everything it encounters regardless of the limits you set for the memory cache, up to a certain percentage of total available memory. In recent versions of the browser, most internal memory management settings not in the preferences file seem to be set to "-1" (fully automatic) so there's no way to change them unless you recompile. Bloody annoying.
Not being an application developer, my only lead on how to track down all the settings involves comparing the code of Pale Moon v26 to v27. Not an easy feat, seeing as how there's over 40,000 new or changed files between those two versions. I've not made much progress on compiling a less stupid build, but I do know the problem is that the browser is just insanely greedy with memory, not that it's "losing" it.
I can copy a Windows install disk, and create a working copy without understanding how it works.
Assuming you copier has a 100% understanding of how the structure of the disk works.
I'd like to see you try this approach with a copy-protected floppy disk for one of those 80's computers. Now you need a deep understanding of how the track layout works to make a copy, or else your copy will fail. Even worse, the copied programs on the disk may be corrupted and not work as expected, and perhaps even do something dickish to your computer.
More information about this can be found in Brian Bagnell's book, "Commodore: A Company on the Edge." The original engineers talk quite a bit about how the hardware worked and was developed.
How about a manager deciding to remove the high-speed serial port on the C64, without the engineers' knowledge, because he didn't know what it was for? That resulted in the floppy drive being a hundred times slower than it should have been, since it had to be plugged into the C64's slow serial port instead. Untold hours of peoples' lives were wasted due to that braindead cost-cutting measure, made by someone who had no clue how hardware worked.
I learned a lot about the Amiga just by dicking around. Ramscans were tons of fun, as you could actually see the OS and programs running in memory. I could listening to random blocks of memory play out the speaker and guess what kind of data it was. Actually seeing bitplanes move around and learning about planar graphics taught me a lot about how the computer actually used memory. I wrote a program to sort the graphics display and could see the sort working in realtime and how different sorts compared to each other. I followed the traces on my motherboard and learned it only took 9 address lines to access all the memory in a 512K chip. I build all kinds of custom cables to hook up peripherals that were never meant to be Amiga compatible.
Such fond memories of when you were even able to understand how the computer worked, let alone ALLOWED to.
Honestly, I hated BASIC. Even from the onset, it was obvious that line numbers, gotos everywhere, and the lack of functions/procedures was a nightmare.
I did a lot of work in AMOS Basic on the Amiga, and the only reason why I did is because the free C compilers had no documentation whatsoever, commercial compilers cost more than the machine itself, and I couldn't stand the idea of having to manage pointers everywhere just to open a damn screen or window. Secretly, what I wanted was AMOS libraries with C syntax. BASIC was always an abomination and obviously horrible after the novelty of "Hello World" wore off.
While my Amigas had their problems, I never had anywhere near as many issues with those computers as I have today.
For example, I've had the same installation of OS 3.0 on my Amiga 1200 for the last 25 years. It still works every time I boot it up, and never bitches about having to do maintenance service or does mysterious things in the background. I did copy the OS installation to a new hard drive without modifying anything, and the OS didn't scream at me to retype a license key or otherwise accuse me of piracy. Hell, most of the OS was on a ROM chip, but you could still patch it to the latest version by running the latest "setpatch" executable. The OS didn't needlessly touch or write files every second, so if a crash did happen, it wouldn't leave you with corruption or force you to do a complete filesystem check like Windows and the Mac did.
I recently recaped the A1200 motherboard, and everything still works as well as the first day I bought it. I still use it regularly, and recently dug my A1000 out of storage for restoration. To hell with nostalgia syndrome -- they're still as enjoyable as I remember, and I still love them to bits.
I used Windows at home once Commodore bit the dust, and used Macs extensively at my school. They were never the same, and they just got worse and worse over time, especially after Win2K. Even Linux, which always sucked, has never gotten to the point where is "just works".
You show much hostility to alternate options or choices.
Pretty much the whole point of a distro is to create and manage a turn-key Linux installation, so the choices are made by the distro developers. You can try to hack apart your distro and install the options you want, but it's often pretty difficult. If your distro makes terrible changes, your only real option is to switch to another distro, and that can be even more difficult.
What people are doing is showing hostility towards the choices Canonical has made, which do not reflect the wants of the community. Mark is just butthurt that if he wants to remain relevant, he has to do what the community wants, not what he wants. Boo hoo.
a new home button would break the phone's TouchID functionality, but the button's return-to-home functionality still worked. The phone could still be locked and unlocked as normal by entering a pin number, suggesting that the two functions are separate pieces of software that are not tied together.
The first concern I had was whether the entire button would refuse to work, and that would be bad. If only the security features are disabled, and there are alternate ways to log in, this sounds perfectly reasonable.
Slashdot Mirror
It's a decent series, but it still baffles me how many billions Nintendo has made on a karting game.
Why cant I call column 1's width "x" and ask the renderer to make column 2's width "3x"? Or use these parameters across tables, so that the columns in table 1, table 2 and table 3 are all the same size?
Reworking the rendering engine to do that takes time and money. If web browser developers are going to spend any effort doing something, it'll be to remove features we've been using happily for 15 years, enhancing the user experience with more telemetry, "brand awareness", or fishing for excuse why nobody needs vertical tabs.
To be fair, I used to work in a warehouse where almost everyone was broke, but the parking lot was filled with big-assed SUVs. One of my co-workers kept bragging about how he was going to buy a used Lexus, because he always wanted one. It was real hard to explain to him that replacing a shock absorber on one of those cost as much as a decent used economy car. Obligatory car analogies are so useful because the damn things are so expensive and a good indicator of one's financial responsibility.
Don't even get me started on the flurry of brand new iPhones, being used constantly on the job by people operating dangerous 8-ton machinery.
"Why can't it be both?"
If the subscription model is optional, then that's fine, but I'm worried it will become mandatory. There's no reason why I should keep paying for my small selection of games forever because people like you keep buying tons of crap that isn't good enough to play more than once.
Or Americans expecting to work less, produce less but get paid more than the other 80% of humanity forever.
Yeah, go ahead and say that to the face of somebody working 2 jobs, 60+ hours a week, and is still broke.
I'm pretty sure that my rent and other basic costs are much higher than the rest of the world. Owning a car is pretty much a necessity in our society. We get nothing for our taxes but more potholes, and we have the gall to charge tax penalties for not buying insurance from private companies.
The fertility clinics need to band together and regulate themselves...
Good luck with that.
My dad's Ford has an electronic parking brake, and I still have no idea how to release it. When I borrow his car, I just never use the parking brake. The car also has automatic headlights, and I can't figure out how to turn them on permanently while driving through a tunnel (there's about a ten second delay when the lights are on full auto). Don't even get me started on the radio, with its confusing, built-in media center.
One of the biggest reasons why I own a Subaru WRX is because it's one of the exceedingly few sport cars on the road with tons of manual controls, including a manual transmission. Subaru is known for resisting the trend of too much needless electronics, and their cars sell very well. I wish more cars were that simple and honest. My only complaint is the automatic climate control, which forces me to manually turn off the A/C every single time I turn on the blower.
Then encrypt your backups yourself using your own tools, and THEN put them in the cloud. If your backups are local, you can do what you like with them.
Indeed. I can say a lot of bad things about Firefox, but it never crashes on me. Ever.
I did switch to Pale Moon about 2 years ago, because it's just as stable but way faster. I use Firefox mostly for "broken" web sites that are designed only to work with popular, name-brand browsers.
You know you're a geek when you break everything down to a math problem. This line of thinking while window shopping saves me a ton of money!
On that note, I'd really like to buy a clothes folding machine.
How can users report bugs? There's a mantra that every developer should hide problems, either to save face or because errors are super scary looking.
I almost never get error codes of any sort these days. More and more log files are in binary format and need special tools to read. When there's a bug in the code of a web page, often all I get is a blank screen. Even the classic BSOD now has an emoticon as its primary message.
The cabinets shown in the patent illustration look almost exactly like those used in AmigaDOS v1.x. They even open the same way. The Amiga was released in 1985, and the patent was filed in 1999.
For a supposed bunch of tech enthusiasts, I see the most technophobia on this site. It's really quite pathetic.
Every day that goes by, I see another company locking us out of our products for our own protection, and taking them away from us by force whenever they want.
The electronic equivalent of book burning most definitely scares me. The only thing that's pathetic is that most technophiles I've come across never studied history and just don't give a damn.
Hooray, yet another EULA I have to sign.
In my attempts to track down why Firefox has huge memory problems but Pale Moon v26 does not (and Pale Moon v27 does), I've determined that bad caching policy is responsible for memory consumption, not leaks.
Firefox will cache the hell out of everything it encounters regardless of the limits you set for the memory cache, up to a certain percentage of total available memory. In recent versions of the browser, most internal memory management settings not in the preferences file seem to be set to "-1" (fully automatic) so there's no way to change them unless you recompile. Bloody annoying.
Not being an application developer, my only lead on how to track down all the settings involves comparing the code of Pale Moon v26 to v27. Not an easy feat, seeing as how there's over 40,000 new or changed files between those two versions. I've not made much progress on compiling a less stupid build, but I do know the problem is that the browser is just insanely greedy with memory, not that it's "losing" it.
Nobody with a paycheck pays 0%.
How does Hollywood economics fit into this statement?
I can copy a Windows install disk, and create a working copy without understanding how it works.
Assuming you copier has a 100% understanding of how the structure of the disk works.
I'd like to see you try this approach with a copy-protected floppy disk for one of those 80's computers. Now you need a deep understanding of how the track layout works to make a copy, or else your copy will fail. Even worse, the copied programs on the disk may be corrupted and not work as expected, and perhaps even do something dickish to your computer.
More information about this can be found in Brian Bagnell's book, "Commodore: A Company on the Edge." The original engineers talk quite a bit about how the hardware worked and was developed.
How about a manager deciding to remove the high-speed serial port on the C64, without the engineers' knowledge, because he didn't know what it was for? That resulted in the floppy drive being a hundred times slower than it should have been, since it had to be plugged into the C64's slow serial port instead. Untold hours of peoples' lives were wasted due to that braindead cost-cutting measure, made by someone who had no clue how hardware worked.
This ended when OSes decided they had to update the access time every time they read a file, so reading date requires writing data. How sad.
I learned a lot about the Amiga just by dicking around. Ramscans were tons of fun, as you could actually see the OS and programs running in memory. I could listening to random blocks of memory play out the speaker and guess what kind of data it was. Actually seeing bitplanes move around and learning about planar graphics taught me a lot about how the computer actually used memory. I wrote a program to sort the graphics display and could see the sort working in realtime and how different sorts compared to each other. I followed the traces on my motherboard and learned it only took 9 address lines to access all the memory in a 512K chip. I build all kinds of custom cables to hook up peripherals that were never meant to be Amiga compatible.
Such fond memories of when you were even able to understand how the computer worked, let alone ALLOWED to.
Honestly, I hated BASIC. Even from the onset, it was obvious that line numbers, gotos everywhere, and the lack of functions/procedures was a nightmare.
I did a lot of work in AMOS Basic on the Amiga, and the only reason why I did is because the free C compilers had no documentation whatsoever, commercial compilers cost more than the machine itself, and I couldn't stand the idea of having to manage pointers everywhere just to open a damn screen or window. Secretly, what I wanted was AMOS libraries with C syntax. BASIC was always an abomination and obviously horrible after the novelty of "Hello World" wore off.
While my Amigas had their problems, I never had anywhere near as many issues with those computers as I have today.
For example, I've had the same installation of OS 3.0 on my Amiga 1200 for the last 25 years. It still works every time I boot it up, and never bitches about having to do maintenance service or does mysterious things in the background. I did copy the OS installation to a new hard drive without modifying anything, and the OS didn't scream at me to retype a license key or otherwise accuse me of piracy. Hell, most of the OS was on a ROM chip, but you could still patch it to the latest version by running the latest "setpatch" executable. The OS didn't needlessly touch or write files every second, so if a crash did happen, it wouldn't leave you with corruption or force you to do a complete filesystem check like Windows and the Mac did.
I recently recaped the A1200 motherboard, and everything still works as well as the first day I bought it. I still use it regularly, and recently dug my A1000 out of storage for restoration. To hell with nostalgia syndrome -- they're still as enjoyable as I remember, and I still love them to bits.
I used Windows at home once Commodore bit the dust, and used Macs extensively at my school. They were never the same, and they just got worse and worse over time, especially after Win2K. Even Linux, which always sucked, has never gotten to the point where is "just works".
You show much hostility to alternate options or choices.
Pretty much the whole point of a distro is to create and manage a turn-key Linux installation, so the choices are made by the distro developers. You can try to hack apart your distro and install the options you want, but it's often pretty difficult. If your distro makes terrible changes, your only real option is to switch to another distro, and that can be even more difficult.
What people are doing is showing hostility towards the choices Canonical has made, which do not reflect the wants of the community. Mark is just butthurt that if he wants to remain relevant, he has to do what the community wants, not what he wants. Boo hoo.
From the article:
a new home button would break the phone's TouchID functionality, but the button's return-to-home functionality still worked. The phone could still be locked and unlocked as normal by entering a pin number, suggesting that the two functions are separate pieces of software that are not tied together.
The first concern I had was whether the entire button would refuse to work, and that would be bad. If only the security features are disabled, and there are alternate ways to log in, this sounds perfectly reasonable.