The floor and ceiling gaps actually have a function. Firstly, they allow for better airflow, which is obviously a good thing in a public restroom. Secondly, the floor gaps in particular allow toilet paper to be passed around without having to open the door.
As for your law: Principally yes but I'd give them more time to avoid the construction companies getting too swamped. You could write a three month deadline into the law and advertise your bill a few months before it's signed into law. That might work.
"If we allow people who *identify* as the opposing gender from what their anatomy implies, to use the restroom of the gender to which they identify as, it opens the door for any number of creepy dudes to follow a little girl into a womans restroom and eye her through the crack in the stall door, and when the police ask him about it, all he has to do is say "Oh, well I sexually identify myself as a woman, so i'm allowed to be in there."
Of course it would help if Americans stopped building restrooms where everyone can see everything. If there is a crack in the stall door that allows you to see anything but the occupant's feet you're doing it wrong.
Good point, although this can happen transparently in the background. The method should still be called asynchronously because you have no idea whether a call will be made and how long it's going to take.
This is not about whether or not support is available, this is about how the API works. The GGP said that existing APIs tend to be too complicated and asked for a simple binary function to check a cert. I pointed out that a function that can return more than just "good" nd "bad" would be more useful. Neither I nor the GGP ever asserted that no API exists at all.
Not binary. I'm thinking of an asynchronous (because CRL servers can be slow) function that returns a status like "valid", "invalid", "self-signed", "expired", "revoked", "known-bad CA" or "request timed out". That way you can check for validity (result == CertificateCheckResult.Valid) but still react appropriately to specific issues, even if it's just to display the appropriate error message. Something like this (in pseudo-C#):
Certificate foo;// magically appears from somewhere var result = await foo.CheckValidity(2000);// timeout in ms
switch (result) { case CertificateCheckResult.Valid: return "It's valid! Hooray!"; case CertificateCheckResult.Expired: return "2old4me"; default: return "I can't be arsed to write code for all the cases. Something is wrong." }
Cyanogen did that, to my knowledge. However, they did stuff like giving one company (OnePlus) a worldwide license without telling them that they gave another company (Micromax) an exclusive license for the Indian market. OnePlus had to develop a different Android distro for India and then decided they'd rather maintain their own distro than keep working with Cyanogen - hence no further Cyanogen-powered OnePlus devices.
If Cyanogen were more considerate of their partners they certainly could have much greater market presence...
Oh, and if they finally got stable COS 13 build done for their top-tier supported devices. And if they followed anything resembling a timely update schedule.
Now if Cyanogen actually starts doing timely updates they may have a selling point. The ZUK Z1 was supposed to get Cyanogen OS 13 before March - it didn't and there is no word on when it will. Right now my phone keeps pestering me about a months-old firmware update that's known to render the tilt sensor effectively useless. Cyanogen couldn't be arsed to fix it so far.
The biggest problem with the Android ecosystem is that there is nobody who gives a shit about it. Google does deliver updates but their Nexus devices are firmly in the unimpressive camp and sometimes downright suck. Remember, these are the flagship devices for the entire platform. Cyanogen kinda sorta does something but if you want anything resembling what they promise you're better off installing unofficial CanogenMod builds someone posted to XDA. Plus, they're so terrible to work with that their OEMs tend to jump ship after one device, vowing to never release a Cyanogen OS device again. Samsung are known to break everything from the Linux kernel to the GUI in innovative ways because apparently their coders have never seen a real Linux before, much less an Android.
Between Apple's ridiculously overpriced hardware and overblown software restrictions, Android's extremely spotty update availability and firmware quality, Microsofts insistence on torpedoing Windows Phone every chance they get and Jolla's poverty-induced everything problems there really is no good smartphone on the market. The best you can hope for is to find the one that is the least terrible. And these are the devices today's world revolves around!
Almost makes you want to go back to a Nokia 6210 and a netbook...
The problem is not that IFTTT offers no value. It does. The problem is that what they ask is gross disproportionate to the value perceived by Pinboard. Had IFTTT just asked Pinboard to implement their new API in a nice manner that could've gotten what they want. But the legal agreement was simply unacceptable and so Pinboard refused.
Now, the legal agreement and the email to the users were a nasty one-two punch: The email makes it look as if it has always been external websites' responsibility to write connectors - which it hasn't. It also makes it look like Pinboard just randomly decided to stop playing and never mentions that the "new platform" comes with huge legal changes. It's understandable that Pinboard is not amused.
In the end it boils down to IFTTT being useful but not useful enough for what they ask. To use yet another analogy: A powerful gaming rig might be nice but if the seller wants 10,000 Dollars for it then it's simply not worth the price. And if the unsuccessful seller later tells everyone how stingy you are because you didn't take up this obviously great offer they're definitely not in the "nice people" camp.
Who's getting pushed out of shape? The CEO just responded to a public announcement by IFTTT that basically told users that Pinboard decided to be incompatible with IFTTT. I don't see them ranting beyond pointing out that "deciding to become incompatible" amounts to not signing a very unfavorable legal agreement. All the vitriol I've seen so far came from/. comments.
You see, coffee machines turn coffee beans into hot coffee which is then further processed into cold coffee through a Brownian deceleration method. In order to turn cold coffee into coffee beans you'd first have to find a way to turn it into hot coffee again - and I don't see any technology like that in the forseeable future.
They'd still suffer a PR hit - they have no way of proving that the things they do to the US version won't affect the rest of the world. Depending on how much that is worth it might be feasible (although admittedly unlikely at this point) to withhold the latest line of iPhones from the US market. The rest of their lineup is fairly unaffected due to not being telecommunications devices so they could continue selling that.
It all boils down to how much it costs Apple to pull out vs. how much it costs them to cooperate. Normally cooperation would be cheaper but depending on just how intrusive the DOJ becomes that might change. In the end my whole point is that no market is invulnerable and must be catered to at any cost, not even a company's home market.
I wonder at which point it becomes more economical to just drop the American market altogether. Sure, the USA are a big and prosperous market but shenanigans like these carry a substantial cost with them - and at some point that cost might exceed the expected profits.
I can see the resoning behind that and I agree that those who cause damage to the most people tend to get off with the slightest punishment, which needs to change. But again, I'd reserve prison sentences for those who actually cause significant harm, such as by pushing people beneath the poverty line or making them homeless. Hotels who block wifi/mobile data access inconvenience their guests and cost the companies who use them for conferences a bit of money - bad but not that bad.
I mean, seriously - look at the GGP's proposal: Fines scaling by an order of magnitude, with the first fine already big enough to completely wipe out smaller businesses. Mandatory jail time for the second offense. That's reminiscent of the War on Drugs: Zero tolerance, cruel punishment and a good chance of causing vastly more damage than the thing it's supposed to protect against.
Sure, white collar criminals deserve proper punishment but that doesn't mean we need to maximize their suffering at any cost, for even the slightest infraction. We can't answer injustice with more injustice and expect a good outcome. It's rather telling that blatantly destructive vengeance fantasies like that get +4, Interesting...
Nah, that is too punishing for smaller venues who might not be aware of the regulations. Better to use day's wages - which for companies should be defined through their annual revenues divided by 365. That way we don't hand out fines that immediately send a small venue into liquidation or go unnoticed by a big venue.
As for jail time: Seriously? For phone/wifi jamming? I mean, sending people to jail for trivialities is all the rage in America these days but I think that reserving that measure for more harmful crimes would be a better policy. Besides, if you just cost the company ten percent of its yearly revenues in fines you will feel the pain - either your boss will want your head or you own the company and it suddenly took a huge financial hit.
Whether using pure O2 in an engine make sense depends on where the engine is used. For a fixed installation it could make sense to use pure oxygen but for something like a vehicle I'd recommend against it - unless you think that vehicle accidents need to become more spectacular.
I do agree, though, that it makes more sense to store the O2 than to vent it. There are plenty of uses for bottles of pure O2.
So how do you adapt such a UI to data? Applications I write are data-driven and the UI:s are generated out of interpreting data from a database. Does Xamarin support that?
You can do UI in C# so a custom control written in C# is what you'll probably go for in this case. Once written, that control behaves like any other so it can be used in XAML pages/controls. The app I'm currently working on actually has some (tame) data-driven pages and it works well.
By the way, since my last comment was downmodded as "Overrated": I'm not really trying to advertise Xamarin here. It's not the best thing since sliced bread. It's pretty good at what it does, though, and if your company is already using C#/WPF it allows you to apply most of your experience with that to app development. Since my company is a C# shop that's a big plus. (While I'm at it: MVVMCross is another framework you might want to consider if writing apps in C#. It goes well with Xamarin.)
Before Xamarin we used Cordova for app development and the main reason why that didn't work out was that the guy who did the app back then barely spoke JS and had no clue about how the DOM works. The quality of the final product is why we decided to go with a more familiar language and framework this time around. Still, it's a good alternative and it avoids Xamarin's long compile times when targeting iOS.
(In case you're wondering: Apple won't allow Mono on iDevices so Xamarin has to talk to a Mac to cross-compile everything to native code. This cross-compilation is done to the entire binary, of course, so even if one single byte is changed you still have to recompile everything. That's the "rickety cross-compilation toolchain" I mentioned earlier. Compiling for Android takes seconds. Compiling for iOS takes minutes.)
I actually consider unified XAML for every platform to be a major feature. You write the UI once and it works everywhere. A few things (mostly margins) might be off on one platform or the other but Xamarin provides a way for you to declare platform-specific values right in the XAML file. Very handy.
Also, I prefer hand-written XAML over Apple's Interface Builder as I never got along well with IB for Cocoa Touch. That's just my personal preference, though.
What? No. Xamarin allows you to develop.Net apps for iOS and Android using Mono (Android) or a rickety cross-compilation toolchain (iOS). These days you use something very similar to the Windows Mobile API (including XAML) to target iOS, Android and WinMo/Metro. It's pretty nifty; I work on a Xamarin-based app and about 95% of the code is shared while the app looks and feels 100% native on all platforms.
I can see Xamarin as something Microsoft would want - now they supply one of the most popular APIs for cross-platform app development.
Note that you're assuming that you are from a country where numbered roads are a thing. In Germany, for example, it's extremely uncommon to use this kind of scheme and even in places where it is used it's often used differently - for example, in Mannheim they enumerate blocks instead of roads and due to the need for the scale to be able to expand in three directions they set it up so that A1 and L1 are adjacent. However, in Europe roads are commonly not straight, which can help with navigation (if you have a map, that is).
Likewise, the nearest mountain could well be a few hundes miles away. Of course any set of landmarks will do but coming from a completely flat area I'm familiar with towns where no landmarks are visible from most places in town.
In such situations I just take out my smartphone and do a map search for whatever is on the road signs. Even just knowing how the current road is laid out can help you get your bearings and if that's not enough you can match the names of crossing roads with what you see on the map to get your exact location. Yes, that's using Google Maps as a road map with a search function. It works fairly well for that and doesn't bulk up your pockets when you're on foot.
Remember that one the biggest enemies of a feminist is a member of a different wave of feminism. If we get a truly random mix of feminists together I'd expect it to take about half an hour before the bulb gets shoved into somebody's eye socket.
Which might count as screwing it in, I guess, so the answer should probably be "one radfem and one libfem".
Road signage should be standardized either at the state or the federal level, depending on who makes the traffic laws. As such, either the state or the federal government should pay 800 Dollars to make the font available to all government entities for government purposes and then everone would be happy. If the new font offers clear enough advantages to switch to it, it should be licensed and mandated for all new signage from then on.
I don't see how anyone would consider it a good idea to have entities small enough to even notice an 800 Dollar dent in their budget license the font individually. Does that mean that municipalities can use whichever font they want for their signage? Why would that ever be considered a good idea? Traffic signage is a clear example of an area where shared standards are better for everyone. Why let people put up whatever they feel like?
While I agree that desk-wide wireless charging is neat I have to wonder how this would impact battery longevity. Sit down at the desk, that's another charge cycle. Still a cool thing, though.
Actually, I got my R9 390 precisely because of quality. Nvidia had this embarrassing thing where the cards they marketed as being DX12 compatible weren't, in fact, fully compatible with DX12. Some missing functionality had to be done in software, at a noticeable performance cost. That's what made me choose AMD as I want my card to last me a few years, probably well into when DX12 will actually matter.
And it's not the first time Nvidia released a product that only technically did what it was supposed to do. I still distinctly remember the GTX 970 which had two gigs of memory, only 1.5 gigs of which you could use without significant performance losses. But hey, technically it had two gigs! You just couldn't use a quarter of the memory.
Recently, every time I was in the market for a GPU, Nvidia's offer was theoretically good but ultimately failed to impress because of some corner they'd cut without informing anyone before launch. AMD might have mediocre drivers and less explicit support from games but at least I don't have to expect zany caveats.
Uh-huh. Once he gets that degree the first thing we'll do is to talk him into taking a sabbatical. Well, it won't take much talking. Even if it means we'll have to take turns providing couches for him to crash on, he really needs some stress-free time. Hopefully that'll help him avoid the worst of it.
If it doesn't he's still fluent in C and there's a lot of unfilled tech jobs around these parts. Not what he dedicated years to getting a degree in but defeinitely much preferable to unemployment.
Slashdot Mirror
The floor and ceiling gaps actually have a function. Firstly, they allow for better airflow, which is obviously a good thing in a public restroom. Secondly, the floor gaps in particular allow toilet paper to be passed around without having to open the door.
As for your law: Principally yes but I'd give them more time to avoid the construction companies getting too swamped. You could write a three month deadline into the law and advertise your bill a few months before it's signed into law. That might work.
"If we allow people who *identify* as the opposing gender from what their anatomy implies, to use the restroom of the gender to which they identify as, it opens the door for any number of creepy dudes to follow a little girl into a womans restroom and eye her through the crack in the stall door, and when the police ask him about it, all he has to do is say "Oh, well I sexually identify myself as a woman, so i'm allowed to be in there."
Of course it would help if Americans stopped building restrooms where everyone can see everything. If there is a crack in the stall door that allows you to see anything but the occupant's feet you're doing it wrong.
Good point, although this can happen transparently in the background. The method should still be called asynchronously because you have no idea whether a call will be made and how long it's going to take.
This is not about whether or not support is available, this is about how the API works. The GGP said that existing APIs tend to be too complicated and asked for a simple binary function to check a cert. I pointed out that a function that can return more than just "good" nd "bad" would be more useful. Neither I nor the GGP ever asserted that no API exists at all.
Cyanogen did that, to my knowledge. However, they did stuff like giving one company (OnePlus) a worldwide license without telling them that they gave another company (Micromax) an exclusive license for the Indian market. OnePlus had to develop a different Android distro for India and then decided they'd rather maintain their own distro than keep working with Cyanogen - hence no further Cyanogen-powered OnePlus devices.
If Cyanogen were more considerate of their partners they certainly could have much greater market presence...
Oh, and if they finally got stable COS 13 build done for their top-tier supported devices. And if they followed anything resembling a timely update schedule.
Now if Cyanogen actually starts doing timely updates they may have a selling point. The ZUK Z1 was supposed to get Cyanogen OS 13 before March - it didn't and there is no word on when it will. Right now my phone keeps pestering me about a months-old firmware update that's known to render the tilt sensor effectively useless. Cyanogen couldn't be arsed to fix it so far.
The biggest problem with the Android ecosystem is that there is nobody who gives a shit about it. Google does deliver updates but their Nexus devices are firmly in the unimpressive camp and sometimes downright suck. Remember, these are the flagship devices for the entire platform. Cyanogen kinda sorta does something but if you want anything resembling what they promise you're better off installing unofficial CanogenMod builds someone posted to XDA. Plus, they're so terrible to work with that their OEMs tend to jump ship after one device, vowing to never release a Cyanogen OS device again. Samsung are known to break everything from the Linux kernel to the GUI in innovative ways because apparently their coders have never seen a real Linux before, much less an Android.
Between Apple's ridiculously overpriced hardware and overblown software restrictions, Android's extremely spotty update availability and firmware quality, Microsofts insistence on torpedoing Windows Phone every chance they get and Jolla's poverty-induced everything problems there really is no good smartphone on the market. The best you can hope for is to find the one that is the least terrible. And these are the devices today's world revolves around!
Almost makes you want to go back to a Nokia 6210 and a netbook...
The problem is not that IFTTT offers no value. It does. The problem is that what they ask is gross disproportionate to the value perceived by Pinboard. Had IFTTT just asked Pinboard to implement their new API in a nice manner that could've gotten what they want. But the legal agreement was simply unacceptable and so Pinboard refused.
Now, the legal agreement and the email to the users were a nasty one-two punch: The email makes it look as if it has always been external websites' responsibility to write connectors - which it hasn't. It also makes it look like Pinboard just randomly decided to stop playing and never mentions that the "new platform" comes with huge legal changes. It's understandable that Pinboard is not amused.
In the end it boils down to IFTTT being useful but not useful enough for what they ask. To use yet another analogy: A powerful gaming rig might be nice but if the seller wants 10,000 Dollars for it then it's simply not worth the price. And if the unsuccessful seller later tells everyone how stingy you are because you didn't take up this obviously great offer they're definitely not in the "nice people" camp.
Who's getting pushed out of shape? The CEO just responded to a public announcement by IFTTT that basically told users that Pinboard decided to be incompatible with IFTTT. I don't see them ranting beyond pointing out that "deciding to become incompatible" amounts to not signing a very unfavorable legal agreement. All the vitriol I've seen so far came from /. comments.
I... don't think it works that way.
You see, coffee machines turn coffee beans into hot coffee which is then further processed into cold coffee through a Brownian deceleration method. In order to turn cold coffee into coffee beans you'd first have to find a way to turn it into hot coffee again - and I don't see any technology like that in the forseeable future.
They'd still suffer a PR hit - they have no way of proving that the things they do to the US version won't affect the rest of the world. Depending on how much that is worth it might be feasible (although admittedly unlikely at this point) to withhold the latest line of iPhones from the US market. The rest of their lineup is fairly unaffected due to not being telecommunications devices so they could continue selling that.
It all boils down to how much it costs Apple to pull out vs. how much it costs them to cooperate. Normally cooperation would be cheaper but depending on just how intrusive the DOJ becomes that might change. In the end my whole point is that no market is invulnerable and must be catered to at any cost, not even a company's home market.
I wonder at which point it becomes more economical to just drop the American market altogether. Sure, the USA are a big and prosperous market but shenanigans like these carry a substantial cost with them - and at some point that cost might exceed the expected profits.
I can see the resoning behind that and I agree that those who cause damage to the most people tend to get off with the slightest punishment, which needs to change. But again, I'd reserve prison sentences for those who actually cause significant harm, such as by pushing people beneath the poverty line or making them homeless. Hotels who block wifi/mobile data access inconvenience their guests and cost the companies who use them for conferences a bit of money - bad but not that bad.
I mean, seriously - look at the GGP's proposal: Fines scaling by an order of magnitude, with the first fine already big enough to completely wipe out smaller businesses. Mandatory jail time for the second offense. That's reminiscent of the War on Drugs: Zero tolerance, cruel punishment and a good chance of causing vastly more damage than the thing it's supposed to protect against.
Sure, white collar criminals deserve proper punishment but that doesn't mean we need to maximize their suffering at any cost, for even the slightest infraction. We can't answer injustice with more injustice and expect a good outcome. It's rather telling that blatantly destructive vengeance fantasies like that get +4, Interesting...
Nah, that is too punishing for smaller venues who might not be aware of the regulations. Better to use day's wages - which for companies should be defined through their annual revenues divided by 365. That way we don't hand out fines that immediately send a small venue into liquidation or go unnoticed by a big venue.
As for jail time: Seriously? For phone/wifi jamming? I mean, sending people to jail for trivialities is all the rage in America these days but I think that reserving that measure for more harmful crimes would be a better policy. Besides, if you just cost the company ten percent of its yearly revenues in fines you will feel the pain - either your boss will want your head or you own the company and it suddenly took a huge financial hit.
Whether using pure O2 in an engine make sense depends on where the engine is used. For a fixed installation it could make sense to use pure oxygen but for something like a vehicle I'd recommend against it - unless you think that vehicle accidents need to become more spectacular.
I do agree, though, that it makes more sense to store the O2 than to vent it. There are plenty of uses for bottles of pure O2.
So how do you adapt such a UI to data? Applications I write are data-driven and the UI:s are generated out of interpreting data from a database. Does Xamarin support that?
You can do UI in C# so a custom control written in C# is what you'll probably go for in this case. Once written, that control behaves like any other so it can be used in XAML pages/controls. The app I'm currently working on actually has some (tame) data-driven pages and it works well.
By the way, since my last comment was downmodded as "Overrated": I'm not really trying to advertise Xamarin here. It's not the best thing since sliced bread. It's pretty good at what it does, though, and if your company is already using C#/WPF it allows you to apply most of your experience with that to app development. Since my company is a C# shop that's a big plus. (While I'm at it: MVVMCross is another framework you might want to consider if writing apps in C#. It goes well with Xamarin.)
Before Xamarin we used Cordova for app development and the main reason why that didn't work out was that the guy who did the app back then barely spoke JS and had no clue about how the DOM works. The quality of the final product is why we decided to go with a more familiar language and framework this time around. Still, it's a good alternative and it avoids Xamarin's long compile times when targeting iOS.
(In case you're wondering: Apple won't allow Mono on iDevices so Xamarin has to talk to a Mac to cross-compile everything to native code. This cross-compilation is done to the entire binary, of course, so even if one single byte is changed you still have to recompile everything. That's the "rickety cross-compilation toolchain" I mentioned earlier. Compiling for Android takes seconds. Compiling for iOS takes minutes.)
I actually consider unified XAML for every platform to be a major feature. You write the UI once and it works everywhere. A few things (mostly margins) might be off on one platform or the other but Xamarin provides a way for you to declare platform-specific values right in the XAML file. Very handy.
Also, I prefer hand-written XAML over Apple's Interface Builder as I never got along well with IB for Cocoa Touch. That's just my personal preference, though.
As someone who uses Xamarin in a commercial product I find this to be very interesting news. Even if it was written in marketingese.
What? No. Xamarin allows you to develop .Net apps for iOS and Android using Mono (Android) or a rickety cross-compilation toolchain (iOS). These days you use something very similar to the Windows Mobile API (including XAML) to target iOS, Android and WinMo/Metro. It's pretty nifty; I work on a Xamarin-based app and about 95% of the code is shared while the app looks and feels 100% native on all platforms.
I can see Xamarin as something Microsoft would want - now they supply one of the most popular APIs for cross-platform app development.
Note that you're assuming that you are from a country where numbered roads are a thing. In Germany, for example, it's extremely uncommon to use this kind of scheme and even in places where it is used it's often used differently - for example, in Mannheim they enumerate blocks instead of roads and due to the need for the scale to be able to expand in three directions they set it up so that A1 and L1 are adjacent. However, in Europe roads are commonly not straight, which can help with navigation (if you have a map, that is).
Likewise, the nearest mountain could well be a few hundes miles away. Of course any set of landmarks will do but coming from a completely flat area I'm familiar with towns where no landmarks are visible from most places in town.
In such situations I just take out my smartphone and do a map search for whatever is on the road signs. Even just knowing how the current road is laid out can help you get your bearings and if that's not enough you can match the names of crossing roads with what you see on the map to get your exact location. Yes, that's using Google Maps as a road map with a search function. It works fairly well for that and doesn't bulk up your pockets when you're on foot.
Remember that one the biggest enemies of a feminist is a member of a different wave of feminism. If we get a truly random mix of feminists together I'd expect it to take about half an hour before the bulb gets shoved into somebody's eye socket.
Which might count as screwing it in, I guess, so the answer should probably be "one radfem and one libfem".
Road signage should be standardized either at the state or the federal level, depending on who makes the traffic laws. As such, either the state or the federal government should pay 800 Dollars to make the font available to all government entities for government purposes and then everone would be happy. If the new font offers clear enough advantages to switch to it, it should be licensed and mandated for all new signage from then on.
I don't see how anyone would consider it a good idea to have entities small enough to even notice an 800 Dollar dent in their budget license the font individually. Does that mean that municipalities can use whichever font they want for their signage? Why would that ever be considered a good idea? Traffic signage is a clear example of an area where shared standards are better for everyone. Why let people put up whatever they feel like?
While I agree that desk-wide wireless charging is neat I have to wonder how this would impact battery longevity. Sit down at the desk, that's another charge cycle. Still a cool thing, though.
Actually, I got my R9 390 precisely because of quality. Nvidia had this embarrassing thing where the cards they marketed as being DX12 compatible weren't, in fact, fully compatible with DX12. Some missing functionality had to be done in software, at a noticeable performance cost. That's what made me choose AMD as I want my card to last me a few years, probably well into when DX12 will actually matter.
And it's not the first time Nvidia released a product that only technically did what it was supposed to do. I still distinctly remember the GTX 970 which had two gigs of memory, only 1.5 gigs of which you could use without significant performance losses. But hey, technically it had two gigs! You just couldn't use a quarter of the memory.
Recently, every time I was in the market for a GPU, Nvidia's offer was theoretically good but ultimately failed to impress because of some corner they'd cut without informing anyone before launch. AMD might have mediocre drivers and less explicit support from games but at least I don't have to expect zany caveats.
Uh-huh. Once he gets that degree the first thing we'll do is to talk him into taking a sabbatical. Well, it won't take much talking. Even if it means we'll have to take turns providing couches for him to crash on, he really needs some stress-free time. Hopefully that'll help him avoid the worst of it.
If it doesn't he's still fluent in C and there's a lot of unfilled tech jobs around these parts. Not what he dedicated years to getting a degree in but defeinitely much preferable to unemployment.