I'm sure they can still find a use for him
3989 posts • joined 18 Jul 2007
I think that a very clear reason he should not be on the ballot paper is he is mentally incapacitated. His obvious narcissistic tendencies clearly interfere with his ability to perform the duties required by the office.
Trump really is a raging arsehole isn't he? It's too bad, because an election where there is only one credible choice is barely a choice at all. It's clear that many people only support Clinton because the alternatives are so, so, so much worse.
"but you could say the same of C++ or Haskell. Is Rust that finicky?"
It's not finicky, it's *anal*. I've never programmed in Haskell but C++ doesn't care if you:
* forgot to delete some object
* call a pointer to an object that is already deleted
* don't lock a data structure shared by two threads causing race conditions
* use references to something which has gone out of scope
* use implicit default copy constructors & assignment operators that don't work on a class with internal pointers
* forgot to make a destructor virtual
* didn't make your class exception safe, including in its constructor / destructor behaviour
* write off the end of a buffer
Rust will kick your ass if you try anything like this and the language is designed to outright prevent some of these issues. Once you write code the compiler accepts it generates code with comparable speed to C++.
Mercurial and Git are so similar that I expect the transition from one to the other is pretty easy. The main reason I'd stick with Git is that it has some excellent front-ends and IDE integration is extremely good. I think if Git didn't exist though we'd be all on Mercurial and completely happy about it too.
As for Rust, it has the potential to be massive but whether it'll reach that potential remains to be seen. I've written a fair amount of code in it and the main takeaway is that code samples look simple but try to write some and it REALLY punishes you at the compile phase. You have to get your lifetimes and borrowing right. But once you do it produces code which is extremely hard to break in the ways that C or C++ would allow - memory leaks, dangling pointers, buffer overflows, data races etc.
That makes it perfect for systems programming but also for security software, network stacks and so on where (deliberately) malformed or corrupted data could break a C++ program. If I were writing anything to do with IoT or with a safety / performance critical function and I was starting from fresh I'd definitely consider Rust.
While I can see pair programming being useful for people joining the team, I really don't see any benefit to enforcing it. People naturally come together to solve problems and naturally divide when working on individual tasks.
Forcing it just slows everyone down to half speed. If I wanted to do that I can browse the web for half the time.
If it's more than 5 developers then it sounds like a waste of money. And knowing Oracle it probably is.
QNX is a good OS but Blackberry devices were no better from using it than Android for using Linux, iOS for using BSD, Windows Phone for using NT. All these devices managed to present modern, efficient user friendly phone experiences. And that's all that matters from a user perspective. The choice of micro or monolithic kernel is a sideshow.
As for IoT devices, I expect the main driver for what kernel / OS they use is what tools are available, how well they work, how much they cost and what if any runtime license does the manufacturer have to pay per unit. Since the tools for Linux are generally excellent and the runtime cost is zero, it's clearly going to be the defacto choice unless there is a reason to choose differently.
There is no reason that a desktop should be written in Java to host Android apps any more than Windows should be written in WinRT to host Windows Store apps. The two can co-exist. Besides which, Java is merely the programming language that most (not all) apps are written with on Android. It says nothing of how the code is packaged or executed.
Secondly, the speed of updates is a totally orthogonal issue.
There wasn't a good reason for ChromeOS and Android to be separate things in the first place. It was just a case of Google's left hand not knowing what the right was doing.
I expect whatever they reveal will be reminiscent of RemixOS which is basically desktop android.
Would be to sell a passthru HDMI device that superimposes the pint glass on the screen. Sell the device to the pub for £500 and let them figure out how to get the Sky sub. For extra law-skirting shadiness, make the device show a smiley face by default but provide an easy way to change the graphic to a pint, e.g. an SD card slot.
One way to improve software is to use languages which prevent you from making mistakes in the first place.
Languages like C++ allow the programmer to do patently dumb things without batting an eyelid. e.g returning a reference to a temporary variable. Or creating implicit constructor / assignment operators for classes that will crash because of pointer member variables. Or allowing assignments in conditions. There are numerous other examples.
Some modern languages are far more strict about such things and work on the philosophy that if you can catch an error at compile time you stop it getting into production. Languages like Rust are uber-strict to the point that getting something to compile is a sado-masochistic ritual but there is no doubt that the code that comes out is higher quality and less prone to failure.
The only reason private browsing mode even exists is so you can surprise your wife by ordering her flowers.
Firefox's PDF viewer is fine for viewing but quite awful for printing. Basically PDF is just rendered into a bitmap via an HTML canvas and then that gets printed as HTML. I don't know if PDFium is better, but if it is then that in itself would be a benefit.
Companies choose the path of least resistance. If that involves staying put until circumstances dictate otherwise then that's what they'll do.
If countries want to force IPV6 then it takes little more effort than legislating compliance and setting a timeline by when it should happen by. If it's not possible to *force* compliance then they can make it extremely uncomfortable to not be in compliance - withdrawal of grants, licenses, tax breaks, government contracts etc.
"That sort of diagnostics should only be possible by plugging something via the OBD2 port."
It's not the same as the diagnostics when you bring your car in to be serviced.
I mean diagnostics that Tesla developers might in their app to test remote functionality like keyless entry, summon etc. The in-house build probably has a page with diagnostics, commands to hit the brakes and other stuff that a dev might need to test features in the car already or features they're in the process of adding. There must even be an API of sorts since there are 3rd party apps like Remote S can control the car remotely.
I agree they've screwed up big time. I expect the fault probably lies in the authentication layer, allowing replay attacks or suchlike. But Tesla should also disable certain commands from having any action when the car is in motion.
But yes Tesla have screwed up bigtime here.
Just because you can't see the commands in the app doesn't mean they're not there in the protocol. Cars have diagnostic modes. Providing you can convince the car to authenticate you it probably doesn't care what command you send over the wire.
All those functions are things that an app for the car might contain. I assume they've just intercepted the traffic between app and car and figured out a way of doing a replay attack or a man in the middle.
I could see merit in both approaches.
Java is already open source so conceivably it could fork whenever it felt like. But Oracle hold the copyrights and probably certain patents so it'd have to be renamed as something else. It's not the first opensource that has walked from Oracle stewardship. Hudson became Jenkins, MySQL became MariaDB and of course OpenOffice became LibreOffice.
Of course companies that use Java tend to be highly conservative and even if it was forked it doesn't mean it would succeed. They'd probably stick with what they had for the support, certification and so on. It's probably that conservatism which explains the slow pace of Java development in the first place.
"What that dosent come up? surely thats grounds to sue MS for aiding and abetting criminals ?"
The same argument could be applied to any social engineering scam although clearly Microsoft are not on the ball with WMV. They should either maintain a whitelist of DRMs they support, or bake them into their product and support no others. There are perhaps 4 or 5 major DRMs in common use and it's not like there is much reason to throw it open to others.
WMV or Windows Media Video is a container format (like MKV, MP4 etc.). It can contain video, audio and other streams that are encoded by any number of codecs. The flaw is that if Windows Media Player doesn't have the right codec / drm to play the video / audio in the WMV, it will offer to download and install it.
It's easy to see how this combined with human nature can trick some people into installing a trojan -
1. New movie appears in a web site claiming to suicide-squad.wmv (or whatever)
2. People download and click on it
3. WMP starts up, offers to download the codecs / drm to play the movie
4. People click through these popups
5. Trojan downloads and installs itself using media framework as the bootstrap
The remedy to this is fairly simple:
* Don't download videos with a .wmv extension. It is a dead format and nobody would EVER use it unless they had malicious intent.
* Don't download movies which claim to be self extracting .exes. Chances are they are trojans / malware.
* Don't download movies which are inside .rar or .zip files. The seeder is trying to prevent you from seeing inside so it's likely malicious in some way, either a trojan, garbage data, or some other kind of trick / scam.
* The only container formats in common use would be mp4, mkv and avi. The only video codecs in common use would be H264, HEVC/H265 and MP4 ASP. There are less common formats like m2ts, MPEG-2 etc. but these are the prevalent ones.
* Use a well tested non-default player like VideoLAN to play videos and set the defaults to launch this instead of WMP.
* Don't install or use software which claim to offer free movies / tv shows unless it comes from a reputable source that has the rights to that content.
I find this hilarious. Apple like to brag about their industrial design and they produce a super shiny version and the first piece of advice they give is, "put your high gloss shiny device in a bump case because we know it's going to scratch". What's the point of buying it at all if you have to hide it away because it will look awful if you don't?
I think he does this because he gets fed up of receiving a bad piece of code and occasionally escalates into a profanity laced but reasoned and critical post to explain why its bad and why it won't be accepted. Presumably these posts do attract attention (clearly The Register is a subscriber if it can generate a cheap story for them) and perhaps that's the point. People read the post, get the message and stop submitting stuff that way.
This doesn't surprise me. I wonder how many people would be interested in swapping out bits of their phone. A few phones like Motorola have tried it and it didn't really take off. All the added complexity of modularity (connectors, bus width, bandwidth, clock, voltage, handshaking etc.) is probably for nought.
I'd rather Google focus on providing design and support for serviceable phones. Something like the Fairphone where it is easy to replace broken screens, dud batteries etc.
I wonder why manufacturers like Acer think gamers want computers with weird angular designs and gaudy neon lights. Maybe some do but I suspect most would be content to have a normal looking computer which just happened to play games exceptionally well.
One does not simply flout copyright law.
TJ Lazer, the show within Robocop.
How many customers are going to live somewhere in range where its safe to land a drone and how often are weather conditions suitable to fly it? A pizza in a box could easily catch a gust of wind and crash a drone. And of course there are hazards like wires, pylons, trees, rain, fog, buildings, night etc.
And I bet animals like seagulls would soon get the knack of attacking drones if there was a delicious pizza hanging underneath it. And people griefing the drone / vandalizing it because it's human nature to do it.
Until someone figures out how to solve these issues I don't see this anything more than a lame PR exercise.
The ANPR camera should really get stuck in police cars. It could be hooked up to a system that automatically alerts the cops of missing road tax, missing insurance, stolen vehicles etc.
The Priv runs Android and people seem very positive about the job they've done customising it. The hardware was criticized for getting very hot though.
"You get what you pay for and looking at the price differential of the Rift and Cardboard it's probably near that of the 2CV versus Roller."
Cardboard isn't exactly cutting edge but it's still easy to discern some very serious issues with VR that apply equally to more expensive headsets. The screendoor effect and bad resolution are not issues restricted to cardboard. Both the Vive and Oculus suffer from them too.
I thought it arrived practically stillborn. It's not that the tech doesn't have promise but the expense of the kit, the tech requirements, the sheer hassle of all the cables, sensors etc, and the general meh-ness of the games means it's just not worth the money.
I wonder if PSVR will fare better. On the one hand it's cheaper than Oculus or Vive but on the other it's no less complex to set up. It was bad enough trying to configure a PS Eye with move controllers, but now people are supposed to do it while effectively blind.
Dave and Busters still uses tokens, but they're issued digitally - you swipe a card and the card account credited for anything you win. And lots of other places still spew out paper tickets.
So a hacked machine could payout a jackpot more than it should, or otherwise distort the outcome, e.g. award free games. Not sure it matters with a pinball machine though since it probably wouldn't payout and anyone motivated to hack a machine simply to get free games isn't really thinking things through.
I assume the coin box is locked and emptied by the premises. Any technician who turned up to service the machine wouldn't have much opportunity to steal cash or undercount the number of credits.
I suppose if the machine happened to be placed exactly where you wanted to spy on someone / something or if the machine paid out tokens / tickets in some kind of Dave & Busters place. Otherwise I don't see much reason for hacking except curiosity. I doubt video arcade games / pinball machines employ much more protection than a locked hatch and a service code to gain access to them.
"Nothing about Kickstarters business model is new or innovative. "
You have to admit it's fairly innovative. They've set up a site that matches suckers with money to hucksters who want to take it from them. And they skim a mere 8% of all the cash flowing from one side to another for this matchmaking service.
The EU and NATO would have been a lot more understanding about the coup if they hadn't seen Erdogan use it as an excuse to conduct a mass purge and take one more step along the path to dictatorship.
Trick question since Stanley Kubrick never died. He has spent the last 17 years building his Mars landing set.
All the better to listen to you my dear
It doesn't matter what they communicate. A system which allows a driver to be inattentive will cause accidents. A system which is in itself is imperfect will cause accidents. Both need to be addressed for the system to be safer than a driver by themselves. So this is a forseeable consequence of bad design.
An analogy might be a factory with a dangerous hydraulic machine. You could put warnings all over the machine saying not to do certain things while it's running and someone still will either through stupidity, inattentiveness or whatever. That is why factories are required to install things safety gates, two handed controls, sensors etc. that automatically shut down the machine if the operator does something that puts them at risk. A car hurtling down the road at 70 mph is a dangerous machine and safety should be treated as importantly as it is in a factory.
Tesla's "autopilot" is actually quite modest and it's easy to see how you might break the problem down and model it - multiple lanes of cars all going the same way, sensors that model the car's surroundings / lane markings, algorithms that maintain speed & distance, algorithms that mark opportunities to overtake, algorithms to avoid / brake hazards based on proximity, control steering / brakes / lights. It's complex no doubt but it can be modeled.
But it requires:
a) The computer is able to see all hazards, act in a predictable way and additionally only engage when the road and conditions are suitable. This is clearly not the case.
b) The car forces the driver's attention. Force the driver to hold the wheel with both hands. Force them to touch a pedal in a certain way. Monitor their head and posture. This is clearly not the case either.
It is the failure of a) and b) which causes accidents. A failure of a) is bad enough but without an attentive human, it's a guaranteed accident. This is a forseeable consequence of not forcing attention, i.e. bad design.
The funny part is Tesla's self drive solution is quite modest. The problems facing mostly or even fully automated cars are multiple factors higher. Perhaps reports of accidents might do something to allow a little bit of reality to creep into the hype about self drive vehicles.
The simple answer is to pick a minimum version of Android as the cutoff and use a cross-section of tablets to test against that cover a range of screen, resolution and performance factors. It's not rocket science.
They don't even have to be *real* devices since they could be virtualized and run as part of an automation suite.
Android is not the same everywhere - different devices have different sized screens, different resolutions and different aspect ratios. Some devices may also lack GPS, a telephone stack and so on. But most of these differences are pretty superficial and easy to deal with providing you write your code properly in the first place and don't make horrible assumptions.
I assume Salesforce hasn't. It's the modern day equivalent of notices on websites that said "This page only works on Internet Explorer 6 and 7 (because it's a heap of crap that makes all kinds of bad assumptions that we could fix but we won't)"
I can spot about 8 things wrong with that snippet.
But on a general point, end of line comments are usually never a good idea. There are exceptions of course, but it's usually clearer to put a comment before a piece of code rather than after it. Especially if the code has a formatter like astyle run over it.
Anyone who has been on a large project knows everyone has their own ideas about indentation, use of spaces / tabs, formatting, braces on end of lines, naming conventions, ordering of #includes, public / private code etc.
You have to have a common coding style or the free-for-all becomes a dog's dinner with a greater chance of bugs being introduced. In addition patches can become a real mess if someone reformats a style or mixes their own style in with the rest of the other code.
I'm hardly surprised that the Linux kernel should enforce a coding style. It already has a document for this but oddly the network drivers are excepted from using the normal comment convention. Clearly Linus has gotten so pissed off with this exemption that he's put his foot down. I don't suppose it would be hard to write a perl script that fixed this in a single patch. Probably that will happen if it hasn't already.
All those loyal longtime staff are an expensive burden when the next wave of layoffs happens. Maybe they're trying to piss them off enough that some leave of their own accord. The company would save far more than the cost of a pen.
If you're stupid enough to download warez from some dodgy site then you get everything you deserve.
I recently entered America (still there) and was treated to nearly 2 hours in a queue as people were greeted with 20 rows of US customs posts with only 3 of them open. Of course to "speed up" the process they had some electronic kiosks to complete some steps of immigration except they roped them all off for some other flight to use and not us.
As a final kick in the balls when I return to the UK I'll probably get another 2 hour queue thanks to their equally bullshit e-borders system which can't cope with families.
And that's on top of the inconvenience and bother of ESTA. The only faint praise I can give to their system was it was slightly less awful than Australia's electronic visa system which takes about 20 minutes a person to complete and only stops short of asking for a stool sample.
Tech companies aren't going to invest any money in the UK when they have no idea what the hell is happening. Same for most industries. They'll just start developing plans to move their centre of operations somewhere else which is part of the EU, e.g. Ireland.
The UK needs to get some certainty into the situation and fast. e.g. fast track plans to join the European Economic Area. It's still a terrible choice compared to remain (all the rules, none of the influence) but its still better than uncertainty.
I downloaded and burned YDL to disc. I'm probably one of the miniscule % of people who bothered with the feature or had any intention of using it. It was neat to get going but in truth YDL ran pretty badly on the PS3 because there was a hypervisor in the way and the CPU wasn't designed for out of order execution. The main use someone might have had for it is to get at the SPUs.
It was hardly surprising Sony dropped the OtherOS when a viable hypervisor attack became possible. It would have been refined into a burnable ISO that would have been used to boot and root the console.