There's definitely some of that going on as developers try to pad their resumes with the likes of go and rust. At least the ruby fad seems to be dying down a bit. I still get way too many recruiters approaching me about ruby positions, and I really don't think I can maintain another production project in that language.
Humans? Have you seen how long it takes to train one of those fucking things? And sure, once you have one with two or three decades of experience, their squishy meatputers can generalize well to things they already know. But it's going to take them another at least couple of years to get particularly good at something they haven't worked with before.
Yup. Really, this is a trivial patent. If no one's patented it yet, it's because it's stupid. It's already infuriating having to switch between an Macbook keyboard at work and an actually good keyboard at home. It'll just be that much worse if the Macbook doesn't actually have any keys to press. However, I still hope they do this as it should make it that much easier to convince management that Macbooks are shit for development work.
If it's a competing activity. What trade secrets are at risk here? If she was a diversity person at IBM, I'm gonna guess that IBM's diversity secrets are "Hire white dudes, outsource to countries where people are brown." If she was doing anything else at IBM, well, IBM and Microsoft haven't really been competitors since IBM scrapped OS/2. They very specifically chose not to compete with Microsoft. Microsoft's OSes for the most part does not run on any IBM hardware platforms anymore. Not since IBM sold their laptop business. If IBM still makes any PC hardware, their market penetration is laughable. I mean, IBM might still have Lotus Notes (Haven't worked there since 2005, but I could see them hanging onto that turd for another couple decades,) but no one actually runs that thing other than IBM. And IBM and Microsoft can't be competing over a server market that Linux dominates. So where's the no-compete violation?
Unless you run an ad blocker AND a Javascript Blocker. Run a browser without them for about 15 minutes and you quickly realize that the experience is so shitty that you'd be better off just not browsing the internet at all.
Trump and the alt right are well on their way to turning the USA into a third world country. I guess that's one way to sort out immigration -- see to it that no one wants to immigrate here.
Annoying. They mean annoying. Like my gmail inbox isn't already clogged with an endless litany of companies I talked to once, terrible tech recruiters working out of India and notifications from people I'm not interested in hearing from. At this rate I may as well just ditch email and go back to old-fashioned snail mail. At least then it costs the sender something to talk to me.
It's not a "small" amount of speed -- the S8 is the first android phone I've used that felt really responsive. Everything prior to that always felt a little sluggish. Unfortunately between its weight and its smooth polish, it's also the first android phone I've used that has really felt like it wanted to take a dive every time I pick it up. That works well for Samsung, I suppose, if you're having to replace your phone due to shattered screens every year (Or every few months.) It feels like kind of a shame to put that beautiful hardware in a clunky case, but I may end up having to.
Every time I tried to use it to look someone up, the address was always held by some corporation clearly designed to hide that information. I don't think the database has actually been useful for at least a couple of decades.
I'm guessing they find out in the next couple decades that the telomere is in place as a biological defense against cancer. So assuming you don't have one of those (like those jellyfish, or the naked mole rat,) AND you don't just eventually melt into a cancerous puddle, that's not going to keep you from getting hit by a bus or falling off a ladder or any of a billion other things that eventually kill so many of us before we die of old age. It probably also doesn't protect us from any of the really nasty diseases we can get while aging. Statistically, eventually something's going to get you even if you don't age. The system is very much designed to kill us. Evolution is looking for an answer, and we're not it.
Some billionaires are looking into having their heads or entire bodies frozen to try to survive until we can cure them, but that's really not much further along than building a pyramid for a dead king. Probably less so when you consider that a couple thousand years from now we'll still remember that dead king's name. I don't think the billionaires of today will be as well remembered.
That's an awful noisy op for a couple hundred grand. Unless part of the CIA's mission statement is to make sure life plays out like a soap opera, anyway.
If there's anyone else in the world who does what you do. Guys who can crap out some Javascript and glue together 15 different frameworks with code from sourceforge are a dime a dozen. How about someone who can write a targeting system for a laser? A SPACE laser! Oh, by the way, they'll need a clearance. And something something ITAR. Good luck finding one of those in Mumbai!
And yes, I'd be happy to write your space laser guidance system at home. After the last "Bring your child to work day," the entire office shut down with the dire flu for an entire goddamn week!
Yeah, it would have been less complex to do that application as a webapp. Browser caching of imagery that had already been downloaded would probably have been enough caching on the client side and it would have been persistent across restarts of the application. A lot of the problems that we had with it were due to assumptions of the original design, including running the programs on our server and pushing pixels out to machines that were just as capable but which were being used just as dumb display devices. None of the programs were particularly complex in terms of what they were doing, but they were pushing gigabytes of imagery across the network and the business logic was where the tricky bits were. None of it was commented or enumerated in requirements anywhere, the programs just followed whatever execution path they followed and were executed in an order documented in a few pages on a wiki.
Yup, I've been experimenting with streaming vpx/opus and it's quite simple and should just work with any modern browser. You can do surprising bit of stuff with the video with Javascript, as well. That alone is going to be pretty compelling for any business that wants to do anything with video, even before you factor in not getting sued for trying to use the format for anything without a license.
Looked at 'em, Qt was the only thing that even remotely offered a solution to pushing as many pixels as we needed pushed, but since we'd be talking about rewriting those applications from the ground up, doing it as a webapp would have been a simpler solution. The code was not very well written -- over 400 global variables, some defined in header files shared across three or four executables. And of course all the display logic was in with all the business logic of the applications, with no documentation as to why or when any particular branch in the code would be followed. It was a blast from the past. The company decided the data it was generating wasn't worth the development effort of maintaining it, and I've since moved on to video processing for fun and profit.
I won't disagree with you, but you know sometimes you get a developer boner to make something shiny. A lot of UIs I work with (Android in general and Samsung's version of it in particular) are very shiny, but also infuriating to work with. Unity kind of felt like that, for the few minutes I was ever able to stand it. I like my focus follows mouse and having multiple windows far too much to stand something that wants to arbitrarily deny me those things. Funnily I can make Windows work for me a lot better than OS/X, but I'm heading back toward Linux everywhere, and a nice, clean and simple window manager.
There's a lot of politics around the X design and code base. At some point in the past some XFree86 guy was probably a dick to some future Wayland developer on a forum or in a bug tracker, and the Wayland guy was probably all like "Fuck you! I'm going to make my own GUI, with blackjack and hookers!"
Funnily X11 is a lot like Lisp in that, during the course of rewriting it, they'll probably make exactly the same mistakes and require the same work-arounds until the Wayland is such a steaming pile of shit that some new guy will be all like "Fuck you! I'm going to make my own GUI!" and the cycle will repeat.
Yeah I was doing some big X11 development a couple years ago and was stunned by just how far things haven't progressed since I was looking at Motif in the '90's. In fact the application I was working on was a Motif program, if you can believe it. Oh God that thing was crap, and there was really no way to fix it in X. Oh, in theory you could do some sort of quad-tree thing back with double-buffered bitmaps on the client, but whoops, our clients (Windows running some crappy X11 server) didn't support the double-buffering extension I would have needed to do that. And I still would have had to do all the image management routines myself from scratch. If you're working on a local system with a local server, it has the potential to not completely suck. If you're actually going over the network, you'd probably be better off just writing a webapp or something anyway.
Slashdot Mirror
There's definitely some of that going on as developers try to pad their resumes with the likes of go and rust. At least the ruby fad seems to be dying down a bit. I still get way too many recruiters approaching me about ruby positions, and I really don't think I can maintain another production project in that language.
Humans? Have you seen how long it takes to train one of those fucking things? And sure, once you have one with two or three decades of experience, their squishy meatputers can generalize well to things they already know. But it's going to take them another at least couple of years to get particularly good at something they haven't worked with before.
How do they get cancer? Doesn't that require cell division?
Go offline, set the date back? That's what we used to do for this sort of thing.
Sure, keep telling yourself that, Mr 535827.
Yup. Really, this is a trivial patent. If no one's patented it yet, it's because it's stupid. It's already infuriating having to switch between an Macbook keyboard at work and an actually good keyboard at home. It'll just be that much worse if the Macbook doesn't actually have any keys to press. However, I still hope they do this as it should make it that much easier to convince management that Macbooks are shit for development work.
For all the hardware I won't put on my network, a Huawei MacBook Pro clone tops the list. Or pretty much anything made by them, for that matter.
But you f**k just ONE goat...
If it's a competing activity. What trade secrets are at risk here? If she was a diversity person at IBM, I'm gonna guess that IBM's diversity secrets are "Hire white dudes, outsource to countries where people are brown." If she was doing anything else at IBM, well, IBM and Microsoft haven't really been competitors since IBM scrapped OS/2. They very specifically chose not to compete with Microsoft. Microsoft's OSes for the most part does not run on any IBM hardware platforms anymore. Not since IBM sold their laptop business. If IBM still makes any PC hardware, their market penetration is laughable. I mean, IBM might still have Lotus Notes (Haven't worked there since 2005, but I could see them hanging onto that turd for another couple decades,) but no one actually runs that thing other than IBM. And IBM and Microsoft can't be competing over a server market that Linux dominates. So where's the no-compete violation?
Unless you run an ad blocker AND a Javascript Blocker. Run a browser without them for about 15 minutes and you quickly realize that the experience is so shitty that you'd be better off just not browsing the internet at all.
Trump and the alt right are well on their way to turning the USA into a third world country. I guess that's one way to sort out immigration -- see to it that no one wants to immigrate here.
Annoying. They mean annoying. Like my gmail inbox isn't already clogged with an endless litany of companies I talked to once, terrible tech recruiters working out of India and notifications from people I'm not interested in hearing from. At this rate I may as well just ditch email and go back to old-fashioned snail mail. At least then it costs the sender something to talk to me.
If you can't afford bluetooth headphones, you probably can't afford a $1000 phone either.
It's not a "small" amount of speed -- the S8 is the first android phone I've used that felt really responsive. Everything prior to that always felt a little sluggish. Unfortunately between its weight and its smooth polish, it's also the first android phone I've used that has really felt like it wanted to take a dive every time I pick it up. That works well for Samsung, I suppose, if you're having to replace your phone due to shattered screens every year (Or every few months.) It feels like kind of a shame to put that beautiful hardware in a clunky case, but I may end up having to.
Every time I tried to use it to look someone up, the address was always held by some corporation clearly designed to hide that information. I don't think the database has actually been useful for at least a couple of decades.
Some billionaires are looking into having their heads or entire bodies frozen to try to survive until we can cure them, but that's really not much further along than building a pyramid for a dead king. Probably less so when you consider that a couple thousand years from now we'll still remember that dead king's name. I don't think the billionaires of today will be as well remembered.
That's an awful noisy op for a couple hundred grand. Unless part of the CIA's mission statement is to make sure life plays out like a soap opera, anyway.
And yes, I'd be happy to write your space laser guidance system at home. After the last "Bring your child to work day," the entire office shut down with the dire flu for an entire goddamn week!
I'm guessing 100%, just like everyone else?
Yeah, it would have been less complex to do that application as a webapp. Browser caching of imagery that had already been downloaded would probably have been enough caching on the client side and it would have been persistent across restarts of the application. A lot of the problems that we had with it were due to assumptions of the original design, including running the programs on our server and pushing pixels out to machines that were just as capable but which were being used just as dumb display devices. None of the programs were particularly complex in terms of what they were doing, but they were pushing gigabytes of imagery across the network and the business logic was where the tricky bits were. None of it was commented or enumerated in requirements anywhere, the programs just followed whatever execution path they followed and were executed in an order documented in a few pages on a wiki.
Yup, I've been experimenting with streaming vpx/opus and it's quite simple and should just work with any modern browser. You can do surprising bit of stuff with the video with Javascript, as well. That alone is going to be pretty compelling for any business that wants to do anything with video, even before you factor in not getting sued for trying to use the format for anything without a license.
Looked at 'em, Qt was the only thing that even remotely offered a solution to pushing as many pixels as we needed pushed, but since we'd be talking about rewriting those applications from the ground up, doing it as a webapp would have been a simpler solution. The code was not very well written -- over 400 global variables, some defined in header files shared across three or four executables. And of course all the display logic was in with all the business logic of the applications, with no documentation as to why or when any particular branch in the code would be followed. It was a blast from the past. The company decided the data it was generating wasn't worth the development effort of maintaining it, and I've since moved on to video processing for fun and profit.
I won't disagree with you, but you know sometimes you get a developer boner to make something shiny. A lot of UIs I work with (Android in general and Samsung's version of it in particular) are very shiny, but also infuriating to work with. Unity kind of felt like that, for the few minutes I was ever able to stand it. I like my focus follows mouse and having multiple windows far too much to stand something that wants to arbitrarily deny me those things. Funnily I can make Windows work for me a lot better than OS/X, but I'm heading back toward Linux everywhere, and a nice, clean and simple window manager.
Funnily X11 is a lot like Lisp in that, during the course of rewriting it, they'll probably make exactly the same mistakes and require the same work-arounds until the Wayland is such a steaming pile of shit that some new guy will be all like "Fuck you! I'm going to make my own GUI!" and the cycle will repeat.
Yeah I was doing some big X11 development a couple years ago and was stunned by just how far things haven't progressed since I was looking at Motif in the '90's. In fact the application I was working on was a Motif program, if you can believe it. Oh God that thing was crap, and there was really no way to fix it in X. Oh, in theory you could do some sort of quad-tree thing back with double-buffered bitmaps on the client, but whoops, our clients (Windows running some crappy X11 server) didn't support the double-buffering extension I would have needed to do that. And I still would have had to do all the image management routines myself from scratch. If you're working on a local system with a local server, it has the potential to not completely suck. If you're actually going over the network, you'd probably be better off just writing a webapp or something anyway.