Barry retiring Puppy ? Puppy tired Barry ?
Submitted by atang1 on Sat, 08/02/2008 - 14:29.
Puppy had sweet spots, but not smooth enough to do any jobs well. Barely working maybe just it.
I have known Barry for a long time from(since) Framingham. He made the first mistake giving up FVWM(foobar is more perfect a system and more IE compatible) for JWM. Then not going for SeaMonkey(separating out toolbars and taskbars in framebuffers) to replace JWM(lack resolution and mega pixel zoom).
Puppy would have to be different for baby laptops with only USB pipelines and cpu L2 cache on data in nand flash cards. Then instant on with SeaMonkey in execution area as splash screen.
Really strip down all those bloated layers of Linux kernels(IBM S390 mainframe hardware compatibility rather than PC architecture?). SliTaz is interesting, but needs squashfs?
Linux pays only if your blogs have advertizement that pays by the thousand clicks. Have you children do the website clicks for pay? Paypal for donations? Sales for official copies of Puppies for collection(serious collectors also need related notes like in your blogs). Submit all your blogs to all the search engines?
You need time to work on your knowledge for the new computer architecture. Cellphones are the next growing IT market by its formfactor. There is still time to work around cloud computing IT, where serious money is(start thinking in $millions, not $10 per copy).
Puppy is obsolete ? Who inherits ? Puplet instant-on or bust ?
The trend is hardware architecture changes, that obsoletes the many old protocols. Many peripherals can be replaced by USB devices. Linux kernels are/were disk OS, peripheral drivers, and network OS. If you only use L2 cache, you only need browser runtime codes, data storage, and USB packets for network(cloud computing).
Sentimental about giving away the control of Puppy is futile. Interested people are only interested if there is something they can debug or improve, may even substitute your codes.
When the new Puppy derivative is done, it will only be runtime codes of Puppy anyway. Where else can you go? But cloud computing thru 127 USB ports(realtime massive parallel computing using multicores and Posix packets)?
good Luck, Barry.
Be wary of GCC 4.3.34.32 ? Optimized more Ubuntu than Debian ?
When you compile with GCC 3.x.x, Debian and apps only need close to 600 builds to run without much bugs on kernel 2.4.x. Which is nice, even though Debian apps are more kernel independent.
Recent, Ubuntu had many buggy tendencies because GCC had move on to 4.3.x.x. The compiler is tailored more for Ubuntu, Gnome and Mono. But alas, too many skeletons in the closet, or bindings errors in reusable files or modules in library. Many symlinks had to be blacklisted to do the correct symlink for each distro.
Shorter file names will have higher data compression ratio to represent longer(bloated) codes in the file or modules. Always do file names in the best interest of ratio compared with file length.
New cpu design will have firefox commands embedded in hardware which is faster than software. Cloud computing will be SAAS with javascript. Toolbars and taskbars are easier to program with foobar?
It is not going to be fixed in one day. Many developers are using Javascript for cloud computing apps to avoid Linux apps. Linux Foundation is still caught asleep on the wheel. Linus is thinking of retirement too. What are we going to do with puplets, needs serious planning?
Footnote:
Its time to use Ascii code version 2.0. V1.0 was teletype printer codes. We need graphics codes replaced by tcl/tk, gtk+ and qt. And many USB devices and their instructions represented in the ascii codes. Also some of the i986 platform instructions?