You have to look around to understand that our world is dominated by such a co-operation. But as it happens in nature, you can recover your intuition with sensistivity analysis. Which of the two choices is more robust under noise?
In this case he was right. Apple goes away from ObjC. If resources were poured on GNUStep + Clang the whole project would be perished at Apple's will (see Swift). If you want my 2 Cents, re-write it to D. GCC has a D frontend. ObjC development is too costly to invest your limited resources. Apple is a corporate, they do whatever they need to get money even if they choose to betray the 3rd party developers.
However by porting to D I see bright future. C is not an option because the resources are limited.
This is what RMS tells. Support GNU. Nothing special. BSD or GPL is irrelevant. LLDB vs GDB is also irrelevant. Just prioritize good GDB support over LLDB. It is a resource assignment question.
FPC (this is what I have the money to buy) is a good target for code generation. FPC people need a nimrod for Pascal that extends (and not substitutes) the syntax of FPC so that valid pascal is valid pascal-nimrod. In this language they could add functional features. FPC as it is has nothing more to offer to programming. Even if I find C a low level language, I believe it is very good. Nimrod guys seem to have the same opinion.
it is definitely better than c++ for my use cases, but it needs a Boost port. However as with C/Freebasic/C++ it should offer a better type system
I cannot understand why
void print(MyObject obj){
writeln(obj.myStringRepresntation);
}
does not make the compiler complaint that MyObjeect should be marked as const in the signature
Of course type inference should have a way to see that writeln is const (the define it)
Even if writeln is unsafe, the user could put an annotation on the signature
@trust void writeln(const T){//asm code
}
and one could infer that print should mark MyObject as const. D is a good language, but it needs more love.
It is not OK. The mighty JavaFX GUI builder 2.0 dies mysteriously on 8.1 while on 7 it works like a charm. Take in to consideration that 8.1 runs on 2014 hardware while 7 runs on a P4 631 socket 775. The UI is simply distracting.
The problem with Macs is that they no longer distribute the Darwin unixoid for PCs. Otherwise, Windows would have lost much much more, even in the corporate. It is a shame Open/Pure Darwin did not have help from Apple.
Windows 9 changelog
New and exciting in this release
-IE replaced with Firefox
-Notepad replaced with notepad2 (please use Notepad++ for power users)
-Office is deprecated, consider switching to Libreoffice
-cmd is deprecated, to be removed in a future release. Please consider using Conemu
-7-zip is the default for archive handling
-A new POSIX subsystem to gradually replace win32 crap 100% compatible with cygwin. Cygwin is expected to fly performanwise.
-Process hacker has replaced windows system monitor.
- Visual studio for other languages other than D is deprecated. A new release throws away all the crap, make the Shell thin and usable with D.
-C# is deprecated, use D (not Java, they are competitors). We will re-introduce C# through mono. We failed.
-Gnu guix is supported
-If you want to use C/C++ consider moving to mingw. We have already moved.
-Get your updates faster through portable apps.
-Paint is here to stay
-Windows media player leaves. VLC is the default player.
-SEH patents have expired. Who cares, new in this release DWARF-3.
-The GatesBot will build latest versions of over 1000 FOSS apps/libraries nightly for your pleasure. Get them through msys2.
-We love FOSS, we have more recent versions than Linux distros.
Have a nice day.
Open Source will thrive when documents mandate that every device must be accompanied by a document describing how this will be programmed. In other way you buy an NVIDIA card or an smart phone and you get a PDF that gives detailed specification of how software can use the device (not how it is manufactured) to get the advertised functionality. this should extended to all sub-components that interact with the software. Using undocumented functionality should be illegal since it is a means to provide illegal competitive advantage. No blobs.
So, you prove you are lucky. Nothing else. I smoke 20 cigarettes a day I am 37 and have no cancer. So smoke 20 cigarettes a day until 37. You are safe.
I wonder about all these papers claiming fantastic performance with neural nets.
This paper makes me wonder about the perturbation invariance of neural networks. The question is how much perturbation is tolerated? Yes, one can perturb a cat image but how much perturbation leaves the concept of cat invariant is another question. This is a fundamental symmetry. In any case this paper is very big news.
Maybe the inherent problem is that neural networks do not approximate smooth, rather than measurable/continuous functions.
Replace the proprietary junk with an Octacore DSP as a co-processor and do software rendering assisted with extra instructions. If it works with arm, it should work with Intel.
We need a stack and a common low level interface like USB Mass Storage for GFX. Only one driver common to all gfx. Implement OpenGL in hardware and interface with it, nothing else. Open source the GFX interface or create a spec, we need one gfx driver and nothing else.
highly interactive hardware -> you mean NVIDIA ATI hardware? They do not comply to any specification like USB mass storage which can be provided as a file.
A graphics card !IS! a file , the crap by vendors is not a GFX card.
The systems you talk about, are co-processors. So they are not per-se files. But with some engineering from the part of vendors you can view them generally as files, one for each co-processor. Then you upload VM-images through this file and create dynamic files (endpoints) for RPC between host and each VM.
The problem is that you cannot buy a graphics card (like a PCI / USB adapter) . You buy a GFX fused with a co-processor integrated in a very strange proprietary manner.
I do not defend the paradigm, like pthreads it has standed the test of time. Vendors are morons.
They seem to have stopped mingw builds and focus on clang-cl on windows. The problem is that you need the Windows SDK. With most other open source / free compilers this is not necessary. Personally I use mingw in both of its incarnations and the problem is that I cannot download a ready made binary. clang-cl is unusable without windows sdk.
It is not compatible with lcc,pelles,openwatcom,digital mars c SDKs.
I am on a national project requiring to stream opengl framebuffers. I had to replace the old slow system with a new one that does not need a special decoder. Guess what I used. VP9 through gstreamer and it plays nicely with FF/Chrome. However if I have time i will convert it to the SDK provided by Google mainly as a personal project.
this is the reason. We need a standard GPU access API and vendor independent. If the DBs need a GPU to speed up, please use Parallela or support OpenGraphics.
Native graphic card decoder is an inflexible design. OpenCL is a flexible standard. You can accelerate new codecs on it. You don't have to wait for a new card.
And in principle it means one less proprietary driver.
Please stop this graphics card argument argument. The GFX thing is anti-competitive. Actually it should be a math-coprocessor. The display should be handled by another device, eg a framebuffer card that interfaces to and reports capabilites of the monitors. Something like USB/Firewire/Soundblaster extension card. The co-processor is just another device sitting on the bus which could accelerate opengl,openal or openvg or you could not buy it but instead rely on the CPU to do the hard work. But you could still interface to the monitor in standards compliant manner.
Slashdot Mirror
You have to look around to understand that our world is dominated by such a co-operation. But as it happens in nature, you can recover your intuition with sensistivity analysis. Which of the two choices is more robust under noise?
In this case he was right. Apple goes away from ObjC. If resources were poured on GNUStep + Clang the whole project would be perished at Apple's will (see Swift). If you want my 2 Cents, re-write it to D. GCC has a D frontend. ObjC development is too costly to invest your limited resources. Apple is a corporate, they do whatever they need to get money even if they choose to betray the 3rd party developers. However by porting to D I see bright future. C is not an option because the resources are limited.
This is what RMS tells. Support GNU. Nothing special. BSD or GPL is irrelevant. LLDB vs GDB is also irrelevant. Just prioritize good GDB support over LLDB. It is a resource assignment question.
VP9 should be better.
FPC (this is what I have the money to buy) is a good target for code generation. FPC people need a nimrod for Pascal that extends (and not substitutes) the syntax of FPC so that valid pascal is valid pascal-nimrod. In this language they could add functional features. FPC as it is has nothing more to offer to programming. Even if I find C a low level language, I believe it is very good. Nimrod guys seem to have the same opinion.
it is definitely better than c++ for my use cases, but it needs a Boost port. However as with C/Freebasic/C++ it should offer a better type system I cannot understand why void print(MyObject obj){ writeln(obj.myStringRepresntation); } does not make the compiler complaint that MyObjeect should be marked as const in the signature Of course type inference should have a way to see that writeln is const (the define it) Even if writeln is unsafe, the user could put an annotation on the signature @trust void writeln(const T){ //asm code
}
and one could infer that print should mark MyObject as const. D is a good language, but it needs more love.
The only reason to buy a NUC is to have a reference platform for Hackintosh.
It is not OK. The mighty JavaFX GUI builder 2.0 dies mysteriously on 8.1 while on 7 it works like a charm. Take in to consideration that 8.1 runs on 2014 hardware while 7 runs on a P4 631 socket 775. The UI is simply distracting.
The problem with Macs is that they no longer distribute the Darwin unixoid for PCs. Otherwise, Windows would have lost much much more, even in the corporate. It is a shame Open/Pure Darwin did not have help from Apple.
I'm interested
Windows 9 changelog New and exciting in this release -IE replaced with Firefox -Notepad replaced with notepad2 (please use Notepad++ for power users) -Office is deprecated, consider switching to Libreoffice -cmd is deprecated, to be removed in a future release. Please consider using Conemu -7-zip is the default for archive handling -A new POSIX subsystem to gradually replace win32 crap 100% compatible with cygwin. Cygwin is expected to fly performanwise. -Process hacker has replaced windows system monitor. - Visual studio for other languages other than D is deprecated. A new release throws away all the crap, make the Shell thin and usable with D. -C# is deprecated, use D (not Java, they are competitors). We will re-introduce C# through mono. We failed. -Gnu guix is supported -If you want to use C/C++ consider moving to mingw. We have already moved. -Get your updates faster through portable apps. -Paint is here to stay -Windows media player leaves. VLC is the default player. -SEH patents have expired. Who cares, new in this release DWARF-3. -The GatesBot will build latest versions of over 1000 FOSS apps/libraries nightly for your pleasure. Get them through msys2. -We love FOSS, we have more recent versions than Linux distros. Have a nice day.
Open Source will thrive when documents mandate that every device must be accompanied by a document describing how this will be programmed. In other way you buy an NVIDIA card or an smart phone and you get a PDF that gives detailed specification of how software can use the device (not how it is manufactured) to get the advertised functionality. this should extended to all sub-components that interact with the software. Using undocumented functionality should be illegal since it is a means to provide illegal competitive advantage. No blobs.
So, you prove you are lucky. Nothing else. I smoke 20 cigarettes a day I am 37 and have no cancer. So smoke 20 cigarettes a day until 37. You are safe.
I wonder about all these papers claiming fantastic performance with neural nets. This paper makes me wonder about the perturbation invariance of neural networks. The question is how much perturbation is tolerated? Yes, one can perturb a cat image but how much perturbation leaves the concept of cat invariant is another question. This is a fundamental symmetry. In any case this paper is very big news. Maybe the inherent problem is that neural networks do not approximate smooth, rather than measurable/continuous functions.
Replace the proprietary junk with an Octacore DSP as a co-processor and do software rendering assisted with extra instructions. If it works with arm, it should work with Intel.
They could pair the cores with 8-core TI DSP in order to mimize blobs (the a simple framebuffer and an A/D would be enough to have video/audio).
With Wayland/Mir people should consider pushing X totally on user space, like Xming,VcXsrv,XDarwin (and XPhoton R.I.P.) with an SDL fallback.
We need a stack and a common low level interface like USB Mass Storage for GFX. Only one driver common to all gfx. Implement OpenGL in hardware and interface with it, nothing else. Open source the GFX interface or create a spec, we need one gfx driver and nothing else.
highly interactive hardware -> you mean NVIDIA ATI hardware? They do not comply to any specification like USB mass storage which can be provided as a file. A graphics card !IS! a file , the crap by vendors is not a GFX card. The systems you talk about, are co-processors. So they are not per-se files. But with some engineering from the part of vendors you can view them generally as files, one for each co-processor. Then you upload VM-images through this file and create dynamic files (endpoints) for RPC between host and each VM. The problem is that you cannot buy a graphics card (like a PCI / USB adapter) . You buy a GFX fused with a co-processor integrated in a very strange proprietary manner. I do not defend the paradigm, like pthreads it has standed the test of time. Vendors are morons.
They seem to have stopped mingw builds and focus on clang-cl on windows. The problem is that you need the Windows SDK. With most other open source / free compilers this is not necessary. Personally I use mingw in both of its incarnations and the problem is that I cannot download a ready made binary. clang-cl is unusable without windows sdk. It is not compatible with lcc,pelles,openwatcom,digital mars c SDKs.
I am on a national project requiring to stream opengl framebuffers. I had to replace the old slow system with a new one that does not need a special decoder. Guess what I used. VP9 through gstreamer and it plays nicely with FF/Chrome. However if I have time i will convert it to the SDK provided by Google mainly as a personal project.
this is the reason. We need a standard GPU access API and vendor independent. If the DBs need a GPU to speed up, please use Parallela or support OpenGraphics.
Native graphic card decoder is an inflexible design. OpenCL is a flexible standard. You can accelerate new codecs on it. You don't have to wait for a new card. And in principle it means one less proprietary driver. Please stop this graphics card argument argument. The GFX thing is anti-competitive. Actually it should be a math-coprocessor. The display should be handled by another device, eg a framebuffer card that interfaces to and reports capabilites of the monitors. Something like USB/Firewire/Soundblaster extension card. The co-processor is just another device sitting on the bus which could accelerate opengl,openal or openvg or you could not buy it but instead rely on the CPU to do the hard work. But you could still interface to the monitor in standards compliant manner.
I would buy one if it came with Vortex86MX even if its pricier. It would be a competitor to the BeagleBoard but with hopefully more open VGA.
and no gdc integration. These are the items I am most interested about.