Yeah, me too. First the US bashes the palestinians, then they bash the Afghanis, then they bash the Iraqis (again), and now they're lining up to bash the Iranians (or is it the North Koreans?) too. I'm sick and tired of it, alright.
I did full-time telecommuting over a 33.3k modem for 2 years using ppp tunnelled over telnet. The latency was about 60-70% greater than the straight dial-up latency. Otherwise, it was quite stable and fine for running emacs. X11 was painful, but I used it when I needed it. Bandwidth degraded about 15% due to the encapsulation.
> I'd think any civilized country would have a > similar law. Law enforcement agencies cannot pick > the people and the time to enforce the law.
C'mon, we're talking about the United States of bloody America here. The purpose of law in the USA is to create a condition in which everyone is equally vulnerable to being imprisoned and gang raped, so that every one will keep their head down and their mouth shut. This is not a "civilized" country like, say, China, or Saudi Arabia. It's the rabid, frothing, nuclear-bombing madman of the world.
Are you so sure of that? What crime, exactly? Can you refer to U.S. Code?
As I understand it, since I am not making a copy, I'm not violating copyright. Since I'm not benefiting from any copying which is occurring, I am not even subject to credible accusation of vicarious infringement (as in the Napster case), which isn't a crime anyhow -- it's a tort.
Someone downloading from me may or may not be creating a copy illegally, but I have no way of knowing that. I do know that it is *possible* for someone to be using my node to contribute bits to the construction of an illegal copy, but then the same is true of my car parked on the street.
The two historical examples of this that I am aware of are the AMD 29k bit-slice microprocessor series, and the Connection Machine model 1. The CM-1 was unique in that it had commercial sales at scales up to 64K bits wide and used a 1-bit wide distributed memory. The reasons these highly customizable architectures did not persist are twofold: Economy of scale favored the standardized microprocessor (on the hardware end) and they wouldn't run pre-existing software and it was hard to find people who could write decent code for the things (on the software end).
I think that compiler and emulator technologies have risen to a point where the software problem is less serious, and no longer precludes a bit-computer renaissance, but the hardware economy issue has grown to make up for the software problems these architectures faced in the late 80's and early 90's. People just don't generally see the point in paying 10x the $$ for 1/10 of the throughput.
You're looking at conclusions, not reasoning. The evidentiary and rational basis for the conclusion simply isn't in evidence, so it's difficult to adequately critique it.
With reasoning like this, anti-creationists find it easy to dismiss any differing viewpoint.
Re:Remind me what the point is again. Seriously.
on
Open-Source Xbox Modchips
·
· Score: 2, Insightful
Single-service application servers for the home. I can upgrade the mail server while the game and web and fileservers stay up, which saves me from complaints by my other family members.
You can pick up a used Xbox for about $90 now. It's low-power, and compact. If I were operating a business, my stack of Xboxen would be a colocated rack of 1U servers, but as this is not a profit center, I'll go with the disposable bic instead of the classic zippo.
protect the pages with client certificate authent., and put your client key pair on a USB keychain dongle. voila, authenticated access from any web browser.
If a codebase is sufficiently complex and mature so that rewriting raises business issues, you're almost always better off incrementally refactoring. Take one bug at a time, and resolve it by improving design, rather than by adding layers of cruft. Formulate end-design goals, and work towards them incrementally, preserving all current correct behaviours.
Yes, it takes longer than rewriting, in order to achieve 90% of the end goal, but the last 10% is always the deal maker or breaker. If your codebase is decrepit and complex, you almost certainly don't have enough interface definition to rewrite a fully functional replacement. The process of incremental refactoring allows you to simultaneously reverse engineer and document the operative interfaces.
For the home environment, Xboxes make great application servers. I've got a stack of 4, purchased used from Barnes & Noble, two running Apache, one running smtp and pop services, and one acting as a fileserver. The advantage of factoring out these services is that I can upgrade the fileserver without bringing down email or web applications.
Everybody does rename by delete+create, or by moving the repository file. No reason not to automate it, methinks.
Binary deltas would really be good. The easiest would be encoding as ascii hex at the client during commit when the entry is marked -kb. That would take perhaps 20 minutes to implement. Of course the storage would be 3x, but you'd get that back after 2 deltas.
Changesets would also be easy to add. Thing is, you can add the feature, but can you get it back into the distribution?
x64 and ia64 are entirely distinct and incompatible instruction set architectures. you're not going to be able to run your x64 kernel on an ia64 chip. it's not in the least similar or analogous to the ia32 situation.
Slashdot Mirror
Yeah, me too. First the US bashes the palestinians,
then they bash the Afghanis, then they bash the
Iraqis (again), and now they're lining up to bash
the Iranians (or is it the North Koreans?) too.
I'm sick and tired of it, alright.
Your ISP may suck and you may wish to get another ISP.
the parent has goatse.cx issues. follow that
link at your own risk.
It's not that it's Linux -- I could care less
about that. It's that it's open source.
I did full-time telecommuting over a 33.3k modem
for 2 years using ppp tunnelled over telnet.
The latency was about 60-70% greater than the
straight dial-up latency. Otherwise, it was
quite stable and fine for running emacs. X11
was painful, but I used it when I needed it.
Bandwidth degraded about 15% due to the
encapsulation.
That being the case, by RIAA logic, every ISP is
a vicarious and contributory infringer of copyright,
and a lawsuit target.
> I'd think any civilized country would have a
> similar law. Law enforcement agencies cannot pick
> the people and the time to enforce the law.
C'mon, we're talking about the United States of
bloody America here. The purpose of law in the USA
is to create a condition in which everyone is
equally vulnerable to being imprisoned and gang
raped, so that every one will keep their head down
and their mouth shut. This is not a "civilized"
country like, say, China, or Saudi Arabia. It's
the rabid, frothing, nuclear-bombing madman of
the world.
> You are guilty of a crime.
Are you so sure of that? What crime, exactly?
Can you refer to U.S. Code?
As I understand it, since I am not making a copy,
I'm not violating copyright. Since I'm not
benefiting from any copying which is occurring,
I am not even subject to credible accusation of
vicarious infringement (as in the Napster case),
which isn't a crime anyhow -- it's a tort.
Someone downloading from me may or may not be
creating a copy illegally, but I have no way of
knowing that. I do know that it is *possible*
for someone to be using my node to contribute
bits to the construction of an illegal copy,
but then the same is true of my car parked on
the street.
...go for it.
What's stopping you?
broke tonight, and bankrupt for the last 5 years
I always suspected that the real world was
actually a 60km-wide disc, and that there
were transparent screens on the horizon.
take one usb laptop drive. replace cable with laser link.
problem solved.
unless you can't provide adequent line-of-sight, that is.
> 1-bit processors...
The two historical examples of this that I am aware of are the
AMD 29k bit-slice microprocessor series, and the Connection
Machine model 1. The CM-1 was unique in that it had
commercial sales at scales up to 64K bits wide and used a
1-bit wide distributed memory. The reasons these highly
customizable architectures did not persist are twofold: Economy
of scale favored the standardized microprocessor (on the hardware
end) and they wouldn't run pre-existing software and it was
hard to find people who could write decent code for the things
(on the software end).
I think that compiler and emulator technologies have risen to a
point where the software problem is less serious, and no longer
precludes a bit-computer renaissance, but the hardware economy
issue has grown to make up for the software problems these
architectures faced in the late 80's and early 90's. People just
don't generally see the point in paying 10x the $$ for 1/10 of
the throughput.
You're looking at conclusions, not reasoning.
The evidentiary and rational basis for the
conclusion simply isn't in evidence, so it's
difficult to adequately critique it.
With reasoning like this, anti-creationists find
it easy to dismiss any differing viewpoint.
Single-service application servers for the home.
I can upgrade the mail server while the game and
web and fileservers stay up, which saves me from
complaints by my other family members.
You can pick up a used Xbox for about $90 now.
It's low-power, and compact. If I were operating
a business, my stack of Xboxen would be a colocated
rack of 1U servers, but as this is not a profit
center, I'll go with the disposable bic instead of
the classic zippo.
#1 Java also has XML serialization.
.NET in this respect,
#2 You can also introspect bytecode. Admittedly,
it is not as well-developed as
but there are no inherent limits.
#3 I could not care less about, so no comment.
#4 For cross-language, use CORBA. Java makes it
trivial.
protect the pages with client certificate authent.,
and put your client key pair on a USB keychain
dongle. voila, authenticated access from any
web browser.
If a codebase is sufficiently complex and mature
so that rewriting raises business issues, you're
almost always better off incrementally refactoring.
Take one bug at a time, and resolve it by improving
design, rather than by adding layers of cruft.
Formulate end-design goals, and work towards them
incrementally, preserving all current correct
behaviours.
Yes, it takes longer than rewriting, in order to
achieve 90% of the end goal, but the last 10% is
always the deal maker or breaker. If your
codebase is decrepit and complex, you almost
certainly don't have enough interface definition
to rewrite a fully functional replacement. The
process of incremental refactoring allows you to
simultaneously reverse engineer and document the
operative interfaces.
> Any politican would categorize RMS as a "crackpot
> loony that should be completely ignored" in a
> second he opens his mouth.
Kinda like Tony Blair, then.
I'm sorry, but I think you said "fight" when you
meant to say "exercise".
I suggest that you *stop* *pissing* *people* *off*.
For the home environment, Xboxes make great
application servers. I've got a stack of 4,
purchased used from Barnes & Noble, two running
Apache, one running smtp and pop services,
and one acting as a fileserver. The advantage
of factoring out these services is that I can
upgrade the fileserver without bringing down email
or web applications.
ClearCase is appalling bloatware. You're lucky.
Everybody does rename by delete+create, or by
moving the repository file. No reason not
to automate it, methinks.
Binary deltas would really be good.
The easiest would be encoding as ascii hex
at the client during commit when the entry is
marked -kb. That would take perhaps 20 minutes
to implement. Of course the storage would be 3x,
but you'd get that back after 2 deltas.
Changesets would also be easy to add.
Thing is, you can add the feature, but can
you get it back into the distribution?
Smells like bytecode JIT to me.
x64 and ia64 are entirely distinct and incompatible
instruction set architectures. you're not going to
be able to run your x64 kernel on an ia64 chip.
it's not in the least similar or analogous to the
ia32 situation.