I've worked with one of those CNC machines. It ran DOS 3. I tried DOSBox, FreeDos, even DOS 7, 6, 5, no go. Their program to ISA card stuff only worked with DOS 3 quirks. Oh, and network libraries back then weren't worth it.
Good one! More plants that are more productive sounds like more air for us too. Removing damages we added seems to be working to our benefit more than causing new damages.
UnionFS / AUFS is currently used to make Live CDs look writable (via ram).
Using this would prefer the SSD more than the hard-drive it overlays.
Changes Needed:
- add write through
- copy to ssd on read
- if SSD full, delete lesser-used blocks
Actually, opinionated choices are very much the nature of open source. Ubuntu follows this (especially with Quickly, one of its programmer tools), but a better example is PERL, the Pattern Extraction and Reporting Language. It's applied everywhere (in spite of | because) it was designed for such 1 specific purpose.
Sometimes I wonder if we should give up on the DE entirely and have an Eclipse-like arrangement of interrelated pieces that target one specific purpose.
Agreed! I revisited KDE @ 4.3 and was stunned that they hadn't dropped KIOSlaves for something GVFS-like.
I can edit a file in a zip on a samba share all remotely via command-line file tools or by right-click in Nautilus. It can even be a huge file over a slow connection as I only pull down what my editor needs.
Beat malware with hardware auth, no thanks. The only way to avoid malware is peer-reviewed source of a design that cannot be compromised (i.e. Open Source). Preferably free, to invite more eyes.
Recording contracts require all routes that could earn money to be signed away. And of-cource "indie" groups won't sign them.
I too can sit around "Independently" and state how I'd like the world to work, or realize the world has changed and move on.
Why do we need an engine (copyright) to protect this line of work anyway? Where were the mechanisms to protect manual typesetter jobs or calculator salesmen? (before technology replaced them)
No C, no deal for Linux. Lets review your list for GCD, see also:
* Task Parallel Library -.NET
* Java Concurrency
* OpenMP - comparable open standard for C, C++, Fortran
* Intel TBB - C++
* Thread pool pattern - DIY
* Task parallelism - not a lib
* Fastflow - C++
That leaves OpenMP which uses pre-processing to convert hints into threaded behavior. It doesn't solve the incredible challenges simultaneous variable access (and GCD does) making it as much developer risk as without it.
GCD still sounds better (though I've never used either). Comments?
Agreed! Sneaker-nets pirated long before the Internet became a better way. No one's going back to sneaker-nets if more technology provides more effective routes.
Why wait, anyone up to standardizing a drive-by wifi file swapping protocol?
Instead of waiting for Hurd, check out FreeRTOS.org and check out this list of features:
- Preemptable (Linux isn't)
- USB & TCP/IP Implemented
- Multitasking, Mutexes & locks, tasks & co-routines
- 23 architectures. Mostly written in C
- Overflow detect, Free dev tools, Execution tracing
It's isn't Linux or FreeBSD yet, but it (and many other kernels) is coming along well. This includes non-Filesystem kernels and Windows emulation kernels.
I'm not so sure that the name is off-base. Their "single focus" goals are actually a broad range of anti-corporatist laws which paint them as a Robin Hood of sorts, appealing to common youth.
Two party politics would be an improvement over Texas's current elections where only Republican primaries decide your candidates. Your choices:
- The current Governor who is open for selling Texas to the highest bidder.
- A 15-year pro-big-business US Senator who made more spending projects than anyone. Still labelled "conservative" though.
New coke was a distraction to change the "old coke" formula from Sugar to High Fructose Corn Syrup. As this ingredient is illegal in Canada and Mexico you can double-check by reading the label of Coke coming from those areas.
nah, if open source ran 90% of the worlds computers, peer possibilities would solve distribution issues. As for improvements, there would be too many incoming patches to manage in most of the current ways.
And if every corporate IT department managed open source programs, feature requests would be *more* common as users would know they had a good chance of being heard.
maybe
In the world of Free (Gratis + Libre) open source software (FLOSS?) there's little need to waste time patching an older system when everyone has free access to a newer system that's backward compatible. That job is left to distribution owners (like Ubuntu whose October 2008 "LTS" is still patched by them).
This process optimization that allows faster developer progress (including testing) to mean more frequent improvements.
Ideals other than GNU:
Unix: Do 1 thing & do it well
When I found the codec would be *in* Firefox rather than OS libraries, that was trouble. Firefox broke sensible rules right there.
Get some good examples written in Vala/Genie before the whole world goes Python. Most apps don't need Python. Just a few examples and some finding & documentation from someone who knows Python may be enough to get this off the ground. That would end "bindings" and "interpreter startup" issues from desktop Linux OSes.
What we need is URL handoff. .PDF should hand the URL to the PDF viewer and be done with it. Someone who doesn't know what's going on will still get a seamless experience and have nothing to complain about.
I've worked with one of those CNC machines. It ran DOS 3. I tried DOSBox, FreeDos, even DOS 7, 6, 5, no go. Their program to ISA card stuff only worked with DOS 3 quirks. Oh, and network libraries back then weren't worth it.
Good one! More plants that are more productive sounds like more air for us too. Removing damages we added seems to be working to our benefit more than causing new damages.
UnionFS / AUFS is currently used to make Live CDs look writable (via ram). Using this would prefer the SSD more than the hard-drive it overlays.
Changes Needed:
- add write through
- copy to ssd on read
- if SSD full, delete lesser-used blocks
Actually, opinionated choices are very much the nature of open source. Ubuntu follows this (especially with Quickly, one of its programmer tools), but a better example is PERL, the Pattern Extraction and Reporting Language. It's applied everywhere (in spite of | because) it was designed for such 1 specific purpose.
Sometimes I wonder if we should give up on the DE entirely and have an Eclipse-like arrangement of interrelated pieces that target one specific purpose.
Agreed! I revisited KDE @ 4.3 and was stunned that they hadn't dropped KIOSlaves for something GVFS-like.
I can edit a file in a zip on a samba share all remotely via command-line file tools or by right-click in Nautilus. It can even be a huge file over a slow connection as I only pull down what my editor needs.
Beat malware with hardware auth, no thanks. The only way to avoid malware is peer-reviewed source of a design that cannot be compromised (i.e. Open Source). Preferably free, to invite more eyes.
Recording contracts require all routes that could earn money to be signed away. And of-cource "indie" groups won't sign them.
I too can sit around "Independently" and state how I'd like the world to work, or realize the world has changed and move on.
Why do we need an engine (copyright) to protect this line of work anyway? Where were the mechanisms to protect manual typesetter jobs or calculator salesmen? (before technology replaced them)
Tell me (or the nearest laywer) any previous employer who sabotages future employment prospects yet cannot prove employee wrongdoing.
No C, no deal for Linux. Lets review your list for GCD, see also: .NET
* Task Parallel Library -
* Java Concurrency
* OpenMP - comparable open standard for C, C++, Fortran
* Intel TBB - C++
* Thread pool pattern - DIY
* Task parallelism - not a lib
* Fastflow - C++
That leaves OpenMP which uses pre-processing to convert hints into threaded behavior. It doesn't solve the incredible challenges simultaneous variable access (and GCD does) making it as much developer risk as without it.
GCD still sounds better (though I've never used either). Comments?
Agreed! Sneaker-nets pirated long before the Internet became a better way. No one's going back to sneaker-nets if more technology provides more effective routes.
Why wait, anyone up to standardizing a drive-by wifi file swapping protocol?
There, solved that last mile thingy for ya.
....if lock-in wasn't in place.
There, fixed it for ya.
Instead of waiting for Hurd, check out FreeRTOS.org and check out this list of features:
- Preemptable (Linux isn't)
- USB & TCP/IP Implemented
- Multitasking, Mutexes & locks, tasks & co-routines
- 23 architectures. Mostly written in C - Overflow detect, Free dev tools, Execution tracing
It's isn't Linux or FreeBSD yet, but it (and many other kernels) is coming along well. This includes non-Filesystem kernels and Windows emulation kernels.
Right on the other side of the border are fancy all-English-speaking hospitals with American doctors doing procedures the FDA bans.
As long as you're avoiding regulation, go where it's been done for years.
I'm not so sure that the name is off-base. Their "single focus" goals are actually a broad range of anti-corporatist laws which paint them as a Robin Hood of sorts, appealing to common youth.
Two party politics would be an improvement over Texas's current elections where only Republican primaries decide your candidates. Your choices:
- The current Governor who is open for selling Texas to the highest bidder.
- A 15-year pro-big-business US Senator who made more spending projects than anyone. Still labelled "conservative" though.
You are.
New coke was a distraction to change the "old coke" formula from Sugar to High Fructose Corn Syrup. As this ingredient is illegal in Canada and Mexico you can double-check by reading the label of Coke coming from those areas.
Thank you for your example.
White males are the "accepted" group to put down for anything. Watch any murder mystery shows lately? They white husband is always the criminal.
Agreed! Once you record a whole day, during sleep times your Bluetooth life recorder's data dump can be walked to:
- Find & delete "Boring Times"
- Recognize, Tag, & delete Media
- Tag anything else useful
- Compress remaining content to [[Device Controller's]] liking.
nah, if open source ran 90% of the worlds computers, peer possibilities would solve distribution issues. As for improvements, there would be too many incoming patches to manage in most of the current ways.
And if every corporate IT department managed open source programs, feature requests would be *more* common as users would know they had a good chance of being heard.
maybe
Open source is made in few ways:
- Corporate Sponsorship
- Independent contributions
- Support Contracts
It appears corporate sponsorship and corporate contributions are the most effective.
Less an expert, more a pattern-finder response:
In the world of Free (Gratis + Libre) open source software (FLOSS?) there's little need to waste time patching an older system when everyone has free access to a newer system that's backward compatible.
That job is left to distribution owners (like Ubuntu whose October 2008 "LTS" is still patched by them).
This process optimization that allows faster developer progress (including testing) to mean more frequent improvements.
Ideals other than GNU:
Unix: Do 1 thing & do it well
When I found the codec would be *in* Firefox rather than OS libraries, that was trouble. Firefox broke sensible rules right there.
Options:
Buy h264: Won't happen. Would you sell it? Not in our patent system where it's "property" without a property value or eminent domain laws.
Firefox gains h264: And becomes "impure" open source or moves out of the USA. Possible but unlikely.
Move sites to $FREE_CODEC: h264 videos are already everywhere since Flash used them. Not gonna happen.
Firefox uses OS Libraries: It stays clean and users/maintainers add what they want.
Get some good examples written in Vala/Genie before the whole world goes Python. Most apps don't need Python. Just a few examples and some finding & documentation from someone who knows Python may be enough to get this off the ground. That would end "bindings" and "interpreter startup" issues from desktop Linux OSes.
What we need is URL handoff.
.PDF should hand the URL to the PDF viewer and be done with it. Someone who doesn't know what's going on will still get a seamless experience and have nothing to complain about.