If I typed that correctly then it should give users on IE8 and below jQuery 1, while everyone else gets jQuery 3 even if their browsers don't support conditional comments. Just be sure not to use any functionality that's not in the jQuery 1 version that you use, but that should be easy.
Should have gone to the Elon Musk Shelter instead. There's so much with all the battery that's happening he wouldn't even need to build that factory anymore.
In 2017 you will get into your car and set off to work and find your fucking brake cables have been cut by Microsoft employees because you didn't upgrade to Windows 10.
Your widow later discovers there's actually a provision for them to do that, in the latest revised EULA - one that was carefully printed out by a Microsoft lawyer onto a single sheet of A4 in Redmond on November 9th 2016 and immediately shredded, thereby gaining the consent of every windows user in the world.
Fuck you, you fucking fucks.
After our vehicle upgrade agents spent all night cutting the brake cables from every car in the neighbourhood, people started complaining that their brakes pedals weren't working. So we fixed that problem by sending our agents out again, this time to remove the brake pedals from all the cars, but for some reason people still whined.
Yeah, I don't know why everyone is complaining that we removed the pedal that they were complaining was broken.
It only shows it doesn't matter what we do at this point, the haters are out for blood and won't see reason. Best to ignore them at this point I suppose..
Ctrl shift escape, you mean. That opens the task manager (which GP has possibly overridden with Process Explorer). Ctrl alt escape is for pushing the active window to the bottom.
Duckie should be roughly similar to Bing, since that's where it draws its search results. There might be some differences due to the fact that DuckDuckGo prevents Bing from tracking you, which limits how much the search results can be customised for you.
Give it a try - I hear that it works well (Bing has improved immensely since it first appeared). If you aren't happy with the results and prefer Google's, but still want to avoid being tracked, then try using StartPage. It's an anonymous search engine, like DuckDuckGo, but it uses Google to generate search results, which I find to be better.
The statement is "the cross-platform alternative to DirectX 12" - specifically 12, and not DirectX in general. On Windows your options for Mantle-like APIs are currently Vulkan and DirectX 12, i.e. the platform-limited alternative to Vulkan is DirectX 12, and the cross-platform alternative to DirectX 12 is Vulkan. I hope that helps you feel a bit better about the headline.
Sounds like you want Firefox Extended Support Release (ESR). ESR releases receive a major update only once every 10 months, but still receive the same bugfix and security patches as the regular releases. Also, when you do get updated to a new ESR version, you know that it's one that's already been supported as a regular release for 2 months, so there's very little chance of surprise problems.
The current version is Firefox ESR 38, which was released as ESR on 11 August last year. The next one is ESR 45, coming on 31 May, which will last all the way until 21 March next year.
It's not like they start a new version and then sprint to finish the entire thing and do QA and bugfixes all in 6 weeks. That would be ridiculous. If you look at their release history you see that after starting development on a new version it's 4-5 months before it's ready for release, which is quite a realistic timeframe.
NoScript is an extension, not a plugin. Those are two completely different kinds of addons. Mozilla's quite particular about that distinction.
Extensions are the things we all know and love, like uBlock, NoScript, GreaseMonkey etc. Plugins are things like Flash, the Java web plugin for running applets, Google Update, Silverlight, and so on. For the most part we really don't need plugins.
Pardon me for replying to your signature rather than your actual post, but if it acquires resources on instantiation like a duck, then isn't it actually an auto_ptr<Duck> rather than a shared_ptr<Duck>?
I didn't say that those are radio buttons, and I don't misunderstand how the poll is set up. You assume (as did I, and probably the creator of the poll) that it's possible to submit with both boxes unchecked, but in fact the poll does not allow it. That's the reason I'm pointing it out.
A poll is a good idea, but this one's unlikely to give useful results because of two problems:
- As it stands now, in order to declare that you don't use tab groups you'd have to vote that you DO use Pocket even though you don't, and vice versa, so you risk a lot of false data.
- Plenty of people will notice that you're using a URL shortener when there's no practical reason for doing so, and would be reasonable (if wrong) in assuming that you chose to do so because you firmly believe that few would willingly click on the link if they knew where it goes. As such, a good number of people who would otherwise have participated in your poll instead ignore it, figuring it's probably a goatse prank or something.
I agree completely. We're not using DOS anymore. ".brotli" is concise and indicates the name of the format perfectly well. No need to obfuscate it by trying to shorten it further.
Consider that in the past Chrome, Opera, Firefox, Internet Explorer and many other browsers all used to support the same plugins (which were made according to the Netscape Plugin API). Quite a long time ago IE changed to its own plugin API (ActiveX *shudder*), and Chrome now uses the Pepper Plugin API. There's no reason all the other browsers couldn't eventually move over to PPAPI (or some other one, but PPAPI looks like the best at the moment) and it would be like the old days when plugins didn't need to be made over and over for each individual browser.
This is great news. Firefox is my browser of choice, but having written extensions for both Firefox and Chrome I must say that Chrome is far easier to develop for.
I wasn't expecting this, but it makes sense - with Mozilla focusing on Electrolysis (their project to make Firefox multi-process) the existing API wouldn't work well because it wasn't designed with a multi-process browser in mind. I was expecting them to design a whole new API and then have to go through extensions breaking every few updates as the new API stabilised. Going with an existing API that's already mature and known to work for exactly the kind of architecture they're going for will make the transition a lot easier for both the browser devs and extension authors.
Slashdot Mirror
<!--[if lte IE8]> <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script> <![endif]-->
<!--[if !lte IE8]> <!--> <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.0.whatever/jquery.min.js"></script> <!-- <![endif]-->
If I typed that correctly then it should give users on IE8 and below jQuery 1, while everyone else gets jQuery 3 even if their browsers don't support conditional comments. Just be sure not to use any functionality that's not in the jQuery 1 version that you use, but that should be easy.
Should have gone to the Elon Musk Shelter instead. There's so much with all the battery that's happening he wouldn't even need to build that factory anymore.
In 2017 you will get into your car and set off to work and find your fucking brake cables have been cut by Microsoft employees because you didn't upgrade to Windows 10.
Your widow later discovers there's actually a provision for them to do that, in the latest revised EULA - one that was carefully printed out by a Microsoft lawyer onto a single sheet of A4 in Redmond on November 9th 2016 and immediately shredded, thereby gaining the consent of every windows user in the world.
Fuck you, you fucking fucks.
After our vehicle upgrade agents spent all night cutting the brake cables from every car in the neighbourhood, people started complaining that their brakes pedals weren't working. So we fixed that problem by sending our agents out again, this time to remove the brake pedals from all the cars, but for some reason people still whined.
Yeah, I don't know why everyone is complaining that we removed the pedal that they were complaining was broken.
It only shows it doesn't matter what we do at this point, the haters are out for blood and won't see reason. Best to ignore them at this point I suppose..
Yeah only cause Slackware hasn't been updated since 2012...lets install Windows 95 while were at it.
Slackware was last updated on the 15th of April 2016
Ctrl shift escape, you mean. That opens the task manager (which GP has possibly overridden with Process Explorer). Ctrl alt escape is for pushing the active window to the bottom.
Windows Zero-Day Affecting All OS Versions On Sale For $90,000
Thankfully the OS version I'm using isn't on sale for $90,000 so it isn't affected by this zero-day.
Duckie should be roughly similar to Bing, since that's where it draws its search results. There might be some differences due to the fact that DuckDuckGo prevents Bing from tracking you, which limits how much the search results can be customised for you.
Give it a try - I hear that it works well (Bing has improved immensely since it first appeared). If you aren't happy with the results and prefer Google's, but still want to avoid being tracked, then try using StartPage. It's an anonymous search engine, like DuckDuckGo, but it uses Google to generate search results, which I find to be better.
Probably has more space than a Nomad though
It's amazing what you'd be willing to eat when the alternative's pilot bread.
The statement is "the cross-platform alternative to DirectX 12" - specifically 12, and not DirectX in general. On Windows your options for Mantle-like APIs are currently Vulkan and DirectX 12, i.e. the platform-limited alternative to Vulkan is DirectX 12, and the cross-platform alternative to DirectX 12 is Vulkan. I hope that helps you feel a bit better about the headline.
Sounds like you want Firefox Extended Support Release (ESR). ESR releases receive a major update only once every 10 months, but still receive the same bugfix and security patches as the regular releases. Also, when you do get updated to a new ESR version, you know that it's one that's already been supported as a regular release for 2 months, so there's very little chance of surprise problems.
The current version is Firefox ESR 38, which was released as ESR on 11 August last year. The next one is ESR 45, coming on 31 May, which will last all the way until 21 March next year.
Hope that helps you.
It's not like they start a new version and then sprint to finish the entire thing and do QA and bugfixes all in 6 weeks. That would be ridiculous. If you look at their release history you see that after starting development on a new version it's 4-5 months before it's ready for release, which is quite a realistic timeframe.
NoScript is an extension, not a plugin. Those are two completely different kinds of addons. Mozilla's quite particular about that distinction.
Extensions are the things we all know and love, like uBlock, NoScript, GreaseMonkey etc. Plugins are things like Flash, the Java web plugin for running applets, Google Update, Silverlight, and so on. For the most part we really don't need plugins.
I don't know. It all sounds rather complex.
Mathematics fatal flaw is that it does not account for the irrational human.
It's like they say, irrationality is the square root of all evil.
If you wanna kiss this guy, better learn how to kneel
Because you're very short?
Never mind, I was just displaying my ignorance there :p - auto_ptr is deprecated and shared_ptr serves the same purpose but does it better. Now I know.
Pardon me for replying to your signature rather than your actual post, but if it acquires resources on instantiation like a duck, then isn't it actually an auto_ptr<Duck> rather than a shared_ptr<Duck>?
I didn't say that those are radio buttons, and I don't misunderstand how the poll is set up. You assume (as did I, and probably the creator of the poll) that it's possible to submit with both boxes unchecked, but in fact the poll does not allow it. That's the reason I'm pointing it out.
A poll is a good idea, but this one's unlikely to give useful results because of two problems:
- As it stands now, in order to declare that you don't use tab groups you'd have to vote that you DO use Pocket even though you don't, and vice versa, so you risk a lot of false data.
- Plenty of people will notice that you're using a URL shortener when there's no practical reason for doing so, and would be reasonable (if wrong) in assuming that you chose to do so because you firmly believe that few would willingly click on the link if they knew where it goes. As such, a good number of people who would otherwise have participated in your poll instead ignore it, figuring it's probably a goatse prank or something.
What if I wanted to delete all my .bro files? Would that be legal?
As long as you don't tase them.
I agree completely. We're not using DOS anymore. ".brotli" is concise and indicates the name of the format perfectly well. No need to obfuscate it by trying to shorten it further.
Thanks for that information :)
For now.
Consider that in the past Chrome, Opera, Firefox, Internet Explorer and many other browsers all used to support the same plugins (which were made according to the Netscape Plugin API). Quite a long time ago IE changed to its own plugin API (ActiveX *shudder*), and Chrome now uses the Pepper Plugin API. There's no reason all the other browsers couldn't eventually move over to PPAPI (or some other one, but PPAPI looks like the best at the moment) and it would be like the old days when plugins didn't need to be made over and over for each individual browser.
This is great news. Firefox is my browser of choice, but having written extensions for both Firefox and Chrome I must say that Chrome is far easier to develop for.
I wasn't expecting this, but it makes sense - with Mozilla focusing on Electrolysis (their project to make Firefox multi-process) the existing API wouldn't work well because it wasn't designed with a multi-process browser in mind. I was expecting them to design a whole new API and then have to go through extensions breaking every few updates as the new API stabilised. Going with an existing API that's already mature and known to work for exactly the kind of architecture they're going for will make the transition a lot easier for both the browser devs and extension authors.