I was mostly being sarcastic, but I was also referring to coding assembly or writing C for crappy embedded platforms where one has to debug at the aseembly level, so it is nice to have a language that maps directly to assembly.
The other side of it is that from a designer view, architects hate programmers because very few these days understand how computers actually work and so they do not understand what things are hard for computeres and what things are easy. When things are abstracted as far as perl, it allows a good programmer to write code much more easily, but it also allows a bad programmer to hog a P4 to be able to write a program that could run fine on a 8080 if written in assembly.
gotos are great!, They accurately reflect what the processor actually does. Screw this abstraction stuff, make people learn how to use a computer's strengths instead of writing in some horrid POS like Java or Perl
how about we form a huge union that we could use to negotiate and lobby? Imagine if refusing to pay overtime when forcing engineers/programmers to work an 80 hour week because they are "salaried" (..based on 40 hours...) could cause intel and ibm to shut down for a few weeks.
I agree with your post except the "without too much trouble" part
Re:Sick of Microsoft's Lack of Dedication to Mac
on
Microsoft At Macworld
·
· Score: 1
I'm guessing taht you have already tired VLC? It plays lots of stuff but not the sily DRMed WMPs (I thought there was a drm stripping tool, but I guess not). If you haven't, I recomend giving it a shot, I prefer it over WMP whenever I can use it. (Good chance it won't work with MLB stuff though)
I went along the same path and I'm happy to be back on a mac. I really hated windows, I still like linux, but for the computer that I want to just work, mac rocks.
register shifting is a fucking awesome idea for loop unrolling for one. it could become a part of a OoO core. There were also lots of ideas about how assembly language could inform the core as to what is probably happening, which is a great asset, and even without expanding x86 intel could give some current intructions double meanings as to imply what the code will be doing. Stuff similar to this already exists in branches where a branch can be specified by the compiler as probably taken or probably not taken.
I'd have to dig through the specs again to see more
both spamming and this are crimes of fucking up. perhaps you fucked up one day and emailed an al quaeda guy a copy of matlab because he seemed cool on irc and it was connected to making a bomb and your life was put on hold till you were 60...
um.. do you have __ANY__ idea what 25 years in jail is? that's one's whole career. that is your life. when you come out, you are old and cannot find work and cannor get a job and a good number of the people you knew a re dead and the rest either don't remember you or don't want to talk to you.
30 days in county jail for being a jackass sure, but 25 years?
kinda, it kinda depends what type of instruction they are. the athlon's integer core has 3 decoders that are in the normal order, after fetch, before the reservation stations
>>while Intel expands them when they enter the execution pipeline.
intel now uses a trace cache (as long as they don't kill that and go back to the M for everything) so things are decoding __in the cache__ (well, in the trace cache), but their front end is basically the same, just a lot longer
it's actually not that bad of an idea. x86 has what, 16 registers, while just about all modern designs use a tomasulu's OoO machine to use more than that. VLIWish things are probably the future for a bunch of reasons and code morphing is about the only way I can think of to make it work; the only other way is the stuff that the itanium did, which will also be in future processors, but I don't think that OoO will really go away. This would let x86 have its 16 registers and the core could rewrite the code to use the 64 physical registers instead of having to batter the cache all of the time, and caches are HUGE.
"AMD does some code modification when instructions are loaded into the instruction cache; they expand all the instructions up to a fixed size, like a RISC machine."
Both AMD and intel do this. Many instructions are morphed into multiple internal instructions and more painful instructions are actually handled by strings of microcode (think move that meg of memory from here to there)
what the hell is wrong with you? this whole point of RIGHTS instead of privledges is that they apply to everyone. No ifs, no nothing. They are Rights and we ought be treated by who we forget with them.
Slashdot Mirror
I was mostly being sarcastic, but I was also referring to coding assembly or writing C for crappy embedded platforms where one has to debug at the aseembly level, so it is nice to have a language that maps directly to assembly.
The other side of it is that from a designer view, architects hate programmers because very few these days understand how computers actually work and so they do not understand what things are hard for computeres and what things are easy. When things are abstracted as far as perl, it allows a good programmer to write code much more easily, but it also allows a bad programmer to hog a P4 to be able to write a program that could run fine on a 8080 if written in assembly.
http://www.versiontracker.com/macosx/
and fink. I don't really pay for any software
gotos are great!, They accurately reflect what the processor actually does. Screw this abstraction stuff, make people learn how to use a computer's strengths instead of writing in some horrid POS like Java or Perl
not all of us have shotguns and a lot of people have SUVs, not pickup trucks
[OSX:/bin] jsdobbie% ls
[ csh echo ln ps sh test bash date ed ls pwd sleep zsh cat dd expr mkdir rcp stty zsh-4.1.1 chmod df hostname mv rm sync cp domainname kill pax rmdir tcsh
[OSX:/bin] jsdobbie%
huh?.. I'm running Nicotine behind my browser as well. And it is a Mach like microkernel, not BSD like.
the ones sometimes get bent in cheap cables, that's why you have to buy the expensive ones.
does YDL support the airport extreme?
how about we form a huge union that we could use to negotiate and lobby? Imagine if refusing to pay overtime when forcing engineers/programmers to work an 80 hour week because they are "salaried" (..based on 40 hours...) could cause intel and ibm to shut down for a few weeks.
is power a huge concern or could you put a lightbulb in the enclosure?
I agree with your post except the "without too much trouble" part
I'm guessing taht you have already tired VLC? It plays lots of stuff but not the sily DRMed WMPs (I thought there was a drm stripping tool, but I guess not). If you haven't, I recomend giving it a shot, I prefer it over WMP whenever I can use it. (Good chance it won't work with MLB stuff though)
no.. they will do the same thing that they did with panther. People who bought a mac recently will get it for 20$
I went along the same path and I'm happy to be back on a mac. I really hated windows, I still like linux, but for the computer that I want to just work, mac rocks.
register shifting is a fucking awesome idea for loop unrolling for one. it could become a part of a OoO core. There were also lots of ideas about how assembly language could inform the core as to what is probably happening, which is a great asset, and even without expanding x86 intel could give some current intructions double meanings as to imply what the code will be doing. Stuff similar to this already exists in branches where a branch can be specified by the compiler as probably taken or probably not taken.
I'd have to dig through the specs again to see more
eh, they still have the IP, I think that the technology in the Itanium will be making its way into all of the new chip designs
Iff it had come out on time the world would have changed and colleges would be teaching itanium design, not OoO
it was freaking 15 months late, and it still kicked ass decently well, give them some credit
both spamming and this are crimes of fucking up. perhaps you fucked up one day and emailed an al quaeda guy a copy of matlab because he seemed cool on irc and it was connected to making a bomb and your life was put on hold till you were 60...
Godwin's law is normally used with individuals. I don't think it applies when talking about oppressive governments.
no
plenty of pot smokers tho, and they support terrorism!!!......... with all the pot they buy that's grown mostly in the US.......
yeah, it's pretty stupid
um.. do you have __ANY__ idea what 25 years in jail is? that's one's whole career. that is your life. when you come out, you are old and cannot find work and cannor get a job and a good number of the people you knew a re dead and the rest either don't remember you or don't want to talk to you.
30 days in county jail for being a jackass sure, but 25 years?
>>AMD expands instructions at cache load time,
kinda, it kinda depends what type of instruction they are. the athlon's integer core has 3 decoders that are in the normal order, after fetch, before the reservation stations
>>while Intel expands them when they enter the execution pipeline.
intel now uses a trace cache (as long as they don't kill that and go back to the M for everything) so things are decoding __in the cache__ (well, in the trace cache), but their front end is basically the same, just a lot longer
it's actually not that bad of an idea. x86 has what, 16 registers, while just about all modern designs use a tomasulu's OoO machine to use more than that. VLIWish things are probably the future for a bunch of reasons and code morphing is about the only way I can think of to make it work; the only other way is the stuff that the itanium did, which will also be in future processors, but I don't think that OoO will really go away. This would let x86 have its 16 registers and the core could rewrite the code to use the 64 physical registers instead of having to batter the cache all of the time, and caches are HUGE.
"AMD does some code modification when instructions are loaded into the instruction cache; they expand all the instructions up to a fixed size, like a RISC machine."
Both AMD and intel do this. Many instructions are morphed into multiple internal instructions and more painful instructions are actually handled by strings of microcode (think move that meg of memory from here to there)
what about children?
what the hell is wrong with you? this whole point of RIGHTS instead of privledges is that they apply to everyone. No ifs, no nothing. They are Rights and we ought be treated by who we forget with them.
And they have to run electric pencil