Exactly! That's why I think we should keep building better AI. It'll be AI, which will be traveling out to the stars, not humans.
We could send a probe to a star and once it reaches it, we could simply beam the AI using a transmitter to the probe. Once AI has done its work there, it can be beamed back to Earth (it there is need for that). Build a network of probes and AI can travel between stars at light speed!
You should be able to get Intex Aqua Fish phone (a manufacturer in India). It runs Sailfish 2.0 created by Jolla. (I haven't actually ordered Aqua Fish, so I can't say much about it). Here's one seller in eBay:
The original Jolla phone still runs the latest Sailfish versions as well so it's another option. But the hardware is pretty dated compared to new phones.
Interesting that he mentions Bret Victor. He was actually one of the designers of the much criticised touch bar [1][2]. He is also working on some other changes for Apple.
I got an update to 10.11 El Capitan yesterday, which probably fixes the vulnerability. You can see the fix in Apple's support page, have a look at the bottom of the page about "System Boot":
However, it didn't explain how the debugger can stop again at the breakpoint after the last step? The interrupt command has been replaced with the original command, so the process won't stop again..
Usually the debugger just replaces the breakpoint instruction with the original byte, then resumes execution in a single-step mode that causes the CPU to just execute a single instruction before firing another interrupt. After that, the debugger sets the breakpoint again and resumes normal execution.
When single-stepping, it's necessary to step only one thread, to ensure that other threads don't skip the (temporarily) disabled breakpoint. There's a paper here that discusses one solution to the problems this causes: http://www.bmrtech.com/uploadfile/image/whitepaper/mentorpap...
(You can engineer a deadlock in gdb due to this, e.g., on x64, by stepping over a SYSCALL instruction that reads from a pipe that's about to be filled by another thread. But you're unlikely to experience this in practice, as system calls are wrapped by a glibc function, and you'll probably be stepping over that rather than the instruction directly.)
What would be the purpose of such a simpler vector format?
Several formats already exist for various use cases: PDF for printing, SVG for web graphics (simple content and icons), OpenType fonts for vector based text and SVG as an exchange format between vector graphics apps.
The only use case I can think of is for standalone vector graphics images, but PDF or SVG is often good enough for that.
The thing is, almost nobody is using SVGs on the Web. Usually wikipedia is cited as a website that uses them, when in reality they're rendering them to raster images. They actually have a nice site with the problems they're facing: https://commons.wikimedia.org/wiki/Help:SVG#Creating_SVG_ima...
Other issues are that files might be bigger than pngs and have bad performance.
PNG and JPEG files are also universally usable outside of browsers. Linux systems often use SVGs for icons, but that's basically where the support stops. If I want to include a SVG in a latex I have to convert it to postscript or pdf. If I want to include a SVG into a Word document I have to convert it into an emf (enhanced metafile). You can't use SVGs for cocoa, UIkit, WinForms or MFC applications out of the box. The reason probably is the complexity to support SVGs.
I use SVG graphics almost exclusively nowadays. Browser support is near-universal. Being able to use the same graphics asset in a wide variety of sizes and screen resolutions is immensely convenient. Rather than having numerous copies of a logo (small, large, retina etc) I only have to make one SVG version (and one PNG fall-back if IE8 matters).
Want the logo a bit smaller? Want that little design element bigger? It's incredibly convenient knowing you can change up your design a bit without having to regenerate your graphics.
Of course there are counterexamples but most websites aren't using SVG. Out of the Alexa top 20 only live.com is using svgs everywhere where they make sense and only yahoo.com is using them in some parts of the website.
I have gone in deep with SVG, rendering them inline with backend code that embeds locale specific text and hyperlinks. I am a big fan of 'use' and sprite-sheets. SVG everywhere is what I like, in fact I prefer to embed a PNG in SVG rather than using native images.
I also prefer to work in SVG directly, i.e. not with some export from an Adobe product. Inkscape is helpful at times but normally it is much easier to do one's own primitives than to have some path that does a circle in however many points. It is great when you can do something like an Instagram icon in four lines of SVG (including colour gradients) than the 1.4Mb EPS file provided in their brand resources.
I do scour the web for things in SVG that are to my personal standards of doing it, i.e. cruft free with a sensible viewbox etc. Yet rarely do I find anything that is that good. It is like the difference between HTML and MS Word documents exported to HTML, with proprietary tags etc.
I do not work too well with the graphics team I work with when it comes to SVG - they are still in the print era and not on the same page as me. They are no more able to work with SVG than the Office Manager is able to make the leap from MS Word to editing HTML in 'vi'.
Regarding usability, for 'supported browsers' (no IE 9-) SVG is great. A year ago I would not have thought that.
For us programmer types SVG is accessible, for graphics guys it isn't really. This I like as I can work with my frontend developer on SVG and not really need 'assets' from the graphics guys still stuck with GUI desktop publishing software that should have been left in the 90's where it belongs.
Hey I like SVG too, even doing logos by hand with it. To this purpose I've created this: http://www.gamesfrommars.fr/live-svg-editor/
I have trouble making SVG use each other reliably though.
> PNG and JPEG files are also universally usable outside of browsers.
JPEG files were the standard for photographs before the first browser was written.
PNGs are super easy to support if you don't care about gamma correction, so it's no surprise that they're widely used.
Vector formats are another beast altogether. Notice from your example that you can't include the EMF in latex either, since an EMF is basically a set of windows draw commands. I'm not sure about the current status of Postscript in Word. Years ago you could embed EPS files but they wouldn't display and only print if you had a postscript printer.
My own intuition is that what is wanted here is a vector-graphics Abstract Machine instruction set in the RISC style, where an implementer only has to write and optimize code for a set of orthogonal primitives, and then everything else "falls out" of that.
Such a vector-drawing ISA wouldn't be at all human-readable, but it'd be an excellent object-code format for other vector formats to compile down to.
> What would be the purpose of such a simpler vector format?
To allow simpler implementation for both consumer and creator software. To achieve better performance (lower size, faster parsing and drawing).
> The only use case I can think of is for standalone vector graphics images, but PDF or SVG is often good enough for that.
SVG has some problems as a graphics format, which are highlighted in this thread. I'm not sure about PDF, I never saw it used as a vector image format, so can't judge much about it.
You're right. SVG2 requires full CSS support. CSS brings lots of complexity, like calc(), CSS variables and so on. All that is needed, because web developers use SVG2 inline in HTML documents. It is also becoming more common to embed HTML in SVG. It's going to be one big tag soup. All that is better for the web, but worse as a stable image format.
There are also plans to create SVG-in-OpenType fonts, which would embed SVG inside web fonts. I have very mixed feelings about that. It is nice to have fonts with multiple colors, gradients and animations. On the other hand, do I want to have the same compatibility problems with fonts as I already have with HTML/SVG? I'm almost hoping that SVG-in-OT fails and Microsoft's simpler multi-color font format wins.
It saddens me a bit, actually. SVG had lots of features way before CSS and now they're forced to adopt them to not confuse people who use HTML/CSS. CSS to my knowledge never even tried adopting features in an SVG-compatible way.
Laws about making copies for private use differ from EU country to another. The author is only talking about UK, which has strict laws about copying for private use. For instance, it is illegal to copy CDs [1] or entire books [2] for private use in UK.
In Finland, it is legal to copy CDs (even the ones in public libraries!) [3] and entire books [4] for private use. So, I don't think that 3D printing of furniture is affected in Finland. I can happily continue printing my Ikea chairs.
What about minimum of a non-differentiable function? I've been using something like Nelder–Mead method (downhill simplex method / amoeba method) [1], but it gets slow near the minimum.
We could send a probe to a star and once it reaches it, we could simply beam the AI using a transmitter to the probe. Once AI has done its work there, it can be beamed back to Earth (it there is need for that). Build a network of probes and AI can travel between stars at light speed!