Ditto! And I think there was a problem if you dragged an icon onto itself on the desktop. It would not be seen as just a "move a few pixels", but rather a "start this application with itself as an argument". Although everyone complained about it, they never did solve it while I was active.
There was another funny bug that I used to impress my friends with. There was an image viewer program (I have forgotten the name) which, in a specific version (not earlier or later) if you run it would cause a terminal window (command prompt) to be shown in the wrong place. Instead of showing in the content area of a window, it would show in the icon "window" in the top left of the window title bar, i.e. where you would click to show a menu with "minimize" etc. You could type "dir" and the files would scroll by in that 16x16 or whatnot window.
With today's eyes, OS/2 was rather crappy. However, the alternatives at the time were crappier in many contexts.
Ahh, thanks for the fond memories. I also ran a DOS-based BBS under OS/2 while developing DOS-based games on the same machine. OS/2 was at the time the best platform for DOS program (it wasn't all apps back then) development since it didn't require a reboot whenever the program crashed.
Also - to make it more interesting - there were different versions of the Mach64 hardware. Some of it didn't work well will the drivers (DAMHIK).
Today I think OS/2 has played out its role with all the major OS:es being robust and having more features. I would even go as far as saying that by todays standards, it is rather crappy. However, in those days, the alternatives on PC hardware were crappier (DOS and Win95 crashing if you breathed incorrectly while NT was stable but you couldn't run games, Linux was... just different).
An anecdote though: Around -94 I built some customer-specific hardware and wrote OS/2 software that used it in an industrial environment. A few years ago, they called me and asked if I could build some more hardware since they were expanding. They didn't ask for replacement of the software on a more contemporary platform.
If you enjoy the "Del/Insert" cut/copy/paste keys still working in Windows, I guess that you will also find some pleasure in that you can double-click in the left end of a title bar to close a window, even though there is no visible icon or button there.
1. They have sold millions, so I figure somebody has checked.
It is hard to check encrypted data in an unknown format emanating from closed hard- and software. The can hasn't been around very long. And the software may get updated anytime, e.g. after an audit.
2. If they were actually recording everything, a lot of people would have to be in on the secret.
Perhaps. But the processing can be partitioned so that one hand doesn't know what the other does. People in the collection department think they collect data that will get destroyed once the training algorithms are done with them. The storage people think they get "some data" and their task is to store and index it. The algorithm training people are just happy to get a lot of data and don't care where it comes from and whether it gets deleted.
3. I assume that Amazon is run by greedy bastards, and they wouldn't build a lot of expensive extra capacity into a device if there was no profit in it for them.
If they are greedy bastards (which I would also assume), wouldn't they make the most of what they already have built?
4. If they were spying, and got caught, it would have terrible effects on their reputation, and cost them a lot of customers.
... for a couple of weeks. Then it will be forgotten or ignored by the majority.
Am I thinking wrong, or isn't this potentially a good thing? The more DOS:ers fighting for the same bots, the fewer of them will be able to hit each site. Thus they won't really be effective any longer.
> If the 'C' language were a flawed language then producing code for all those other languages, using 'C' would make all of those languages inherently contain the same systemic flaws.
No! In C it is trivial to create a buffer overrun error/vulnerability. A Java program on a JVM compiled from C would require careful coding to create a buffer overrun.
> It takes a great deal of experience to understand where problems can be produced in any programming language.
Agreed. And to understand that different languages are open to different problems. That goes for system building on levels above the single programs as well.
When is the startup time of a Java program a problem in practice?
Not trolling - could you give me an example?
I work with Java every day, both for tooling and end products. The Java startup times are never a factor. What takes time is dependency management, loading of plugins, synchronization between systems etc, and you are likely to have them using any language. The time from initiating the process to the first line of Java code being executed is hardly measurable in the context.
In the race to make the MBP look lean, clean and smooth, they have forced you to bring a handful of dongles if you want to connect anywhere. You don't look so hip any longer with those dongles protrouding everywhere, and you certainly don't look hip when you have forgotten to bring one for your public presentation.
I agree completely. Apart from for wireless charging, I don't think there is anything amiss with the current versions. The "new version every X months" seems to me to be mainly a marketing thing to (1) show that you still exist and (2) keep the economy flowing in the echosystem of devices and peripherals.
Just a thought: What if they had skipped the generation increase altogether, instead keeping the current generation for another year? Zero new development investment, just continued production. All existing cases and covers would work, just sell more. The only thing missing would be people upgrading to the latest version just because it's new.
By removing the headphone jack, they have ensured that people and media are so busy being upset that they fail to notice that there is nothing relevant new with the '7.
How about if the US government (and others) spent more of the effort protecting their people instead of spying on them? As in helping its citizens to safe(r) communication and storage through technology, legislation and practices instead of letting them be susceptible to any potential enemy and letting them further into the infrastructure.
Sounds like a marketing statement to me. They want us to buy new stuff often; why would they put effort into increasing the life span? The only reason I can see is if the competition is better and they are afraid that customers will chose another brand next time.
If they want to support prolonged ownership of a device, then they should provide security and, preferably, os version upgrades for the same time. That I would pay for (Apple owners do, but I'm in the Android echosystem).
If the width of indentation is a major hurdle for your development, maybe you have greater issues.
It may not look pretty in your eyes. Get over it. Focus on writing good code instead. If you write it first, you get to decide the indentation.:)
Even worse, plenty of developers automatically perform a global re-indent (and re-format, and re-adjust imports) without even thinking as soon as they open a file to make a change. This makes it harder to track the actual changes through source control annotation.
The discussions about tabs vs spaces is a silly, bike-shed habit some developers fall into when they don't have anything important to discuss. Use whatever you feel like. Mix if you must (unless Python), it is no big deal (there, I said it). But please, please, please don't automatically change parts of the source files that you are not conciously touching.
Amazingly, Apple have managed to fail on almost every single one of those bullets in a product they have the stomach to call "Pro". The only thing they have done right - and better than the competition - is the wonderful force touch trackpad. Also, the CPU is ok and the nub is no loss.
Slashdot Mirror
Ditto! And I think there was a problem if you dragged an icon onto itself on the desktop. It would not be seen as just a "move a few pixels", but rather a "start this application with itself as an argument". Although everyone complained about it, they never did solve it while I was active.
There was another funny bug that I used to impress my friends with. There was an image viewer program (I have forgotten the name) which, in a specific version (not earlier or later) if you run it would cause a terminal window (command prompt) to be shown in the wrong place. Instead of showing in the content area of a window, it would show in the icon "window" in the top left of the window title bar, i.e. where you would click to show a menu with "minimize" etc. You could type "dir" and the files would scroll by in that 16x16 or whatnot window.
With today's eyes, OS/2 was rather crappy. However, the alternatives at the time were crappier in many contexts.
Ahh, thanks for the fond memories. I also ran a DOS-based BBS under OS/2 while developing DOS-based games on the same machine. OS/2 was at the time the best platform for DOS program (it wasn't all apps back then) development since it didn't require a reboot whenever the program crashed.
Also - to make it more interesting - there were different versions of the Mach64 hardware. Some of it didn't work well will the drivers (DAMHIK).
Today I think OS/2 has played out its role with all the major OS:es being robust and having more features. I would even go as far as saying that by todays standards, it is rather crappy. However, in those days, the alternatives on PC hardware were crappier (DOS and Win95 crashing if you breathed incorrectly while NT was stable but you couldn't run games, Linux was ... just different).
An anecdote though: Around -94 I built some customer-specific hardware and wrote OS/2 software that used it in an industrial environment. A few years ago, they called me and asked if I could build some more hardware since they were expanding. They didn't ask for replacement of the software on a more contemporary platform.
Honest question: How is this different from the much maligned Java Applet concept?
If you enjoy the "Del/Insert" cut/copy/paste keys still working in Windows, I guess that you will also find some pleasure in that you can double-click in the left end of a title bar to close a window, even though there is no visible icon or button there.
1. They have sold millions, so I figure somebody has checked.
It is hard to check encrypted data in an unknown format emanating from closed hard- and software. The can hasn't been around very long. And the software may get updated anytime, e.g. after an audit.
2. If they were actually recording everything, a lot of people would have to be in on the secret.
Perhaps. But the processing can be partitioned so that one hand doesn't know what the other does. People in the collection department think they collect data that will get destroyed once the training algorithms are done with them. The storage people think they get "some data" and their task is to store and index it. The algorithm training people are just happy to get a lot of data and don't care where it comes from and whether it gets deleted.
3. I assume that Amazon is run by greedy bastards, and they wouldn't build a lot of expensive extra capacity into a device if there was no profit in it for them.
If they are greedy bastards (which I would also assume), wouldn't they make the most of what they already have built?
4. If they were spying, and got caught, it would have terrible effects on their reputation, and cost them a lot of customers.
... for a couple of weeks. Then it will be forgotten or ignored by the majority.
If the Uber drivers are self-employed and work as contractors for Uber, won't the strike just hurt their own personal companies?
Working at a warehouse doing the remaining things that are just a bit too tricky for a robot to do yet
Anyone interested in this train of thought may enjoy reading Manna: http://www.marshallbrain.com/m...
This hack won't work on your iPhone 7. Now they can never turn it into a device that can pick up sounds at any time... Oh...
bilateral agreement
Bilateral as in "you enforce our censorship and we won't imprison the users of your product in our country".
Stop complaining about the damn paywall and pay a subscription to a couple of trusted news outlets.
I want to do just this, but have been unable to identify such outlets. Can anyone give examples?
No?
https://support.apple.com/library/content/dam/edam/applecare/images/en_US/macbookpro/notebook_ports_mul.png
Am I thinking wrong, or isn't this potentially a good thing? The more DOS:ers fighting for the same bots, the fewer of them will be able to hit each site. Thus they won't really be effective any longer.
> If the 'C' language were a flawed language then producing code for all those other languages, using 'C' would make all of those languages inherently contain the same systemic flaws.
No! In C it is trivial to create a buffer overrun error/vulnerability. A Java program on a JVM compiled from C would require careful coding to create a buffer overrun.
> It takes a great deal of experience to understand where problems can be produced in any programming language.
Agreed. And to understand that different languages are open to different problems. That goes for system building on levels above the single programs as well.
Java becoming unusable would be one of the best things that could happen to the IT world.
How so?
When is the startup time of a Java program a problem in practice?
Not trolling - could you give me an example?
I work with Java every day, both for tooling and end products. The Java startup times are never a factor. What takes time is dependency management, loading of plugins, synchronization between systems etc, and you are likely to have them using any language. The time from initiating the process to the first line of Java code being executed is hardly measurable in the context.
About the only pro thing left in the MBP is the price. Limited connectors and no way to upgrade the memory or storage is not pro in my book.
WOW...when the fuck did they do that?!?!?
They ditched it a couple of years ago.
In the race to make the MBP look lean, clean and smooth, they have forced you to bring a handful of dongles if you want to connect anywhere. You don't look so hip any longer with those dongles protrouding everywhere, and you certainly don't look hip when you have forgotten to bring one for your public presentation.
I agree completely. Apart from for wireless charging, I don't think there is anything amiss with the current versions. The "new version every X months" seems to me to be mainly a marketing thing to (1) show that you still exist and (2) keep the economy flowing in the echosystem of devices and peripherals.
Just a thought: What if they had skipped the generation increase altogether, instead keeping the current generation for another year? Zero new development investment, just continued production. All existing cases and covers would work, just sell more. The only thing missing would be people upgrading to the latest version just because it's new.
Absolute brilliant move, Apple!
By removing the headphone jack, they have ensured that people and media are so busy being upset that they fail to notice that there is nothing relevant new with the '7.
How about if the US government (and others) spent more of the effort protecting their people instead of spying on them? As in helping its citizens to safe(r) communication and storage through technology, legislation and practices instead of letting them be susceptible to any potential enemy and letting them further into the infrastructure.
Sounds like a marketing statement to me. They want us to buy new stuff often; why would they put effort into increasing the life span? The only reason I can see is if the competition is better and they are afraid that customers will chose another brand next time.
If they want to support prolonged ownership of a device, then they should provide security and, preferably, os version upgrades for the same time. That I would pay for (Apple owners do, but I'm in the Android echosystem).
In theory, tabs are the right solution. In practice, spaces are the right solution.
-Chris
This! From experience.
If the width of indentation is a major hurdle for your development, maybe you have greater issues. It may not look pretty in your eyes. Get over it. Focus on writing good code instead. If you write it first, you get to decide the indentation. :)
Even worse, plenty of developers automatically perform a global re-indent (and re-format, and re-adjust imports) without even thinking as soon as they open a file to make a change. This makes it harder to track the actual changes through source control annotation.
The discussions about tabs vs spaces is a silly, bike-shed habit some developers fall into when they don't have anything important to discuss. Use whatever you feel like. Mix if you must (unless Python), it is no big deal (there, I said it). But please, please, please don't automatically change parts of the source files that you are not conciously touching.
Amazingly, Apple have managed to fail on almost every single one of those bullets in a product they have the stomach to call "Pro". The only thing they have done right - and better than the competition - is the wonderful force touch trackpad. Also, the CPU is ok and the nub is no loss.