That is my single biggest beef with Python. Whitespace is *not* a character that the interpreter/compiler should care about other than the delimiters between tokens, and literal spaces in strings. (with due exception to the "whitespace" and brainfuck languages).
Well, to be fair you can, even with python, or perl. write script that accepts textfile of op codes, convert opcodes to asm using pack(); write to file in binmode. Simple! (stupid for sure, but simple).
I guess that's really a compiler more than direct... make your compiler able to convert python to asm. there. stupider and still simple.
TL;DR of above: I *dislike* Python (I'm a Perl guy, I want my curlies and semis damnit...). Sure I could contrive to write a driver in a scripting language, but why? If I'm mucking about with IOCTLS I'm in C/C++. If I'm scanning my C driver code for issues, LOC counts, unsafe operators, etc. at a level deeper than the compiler then I'm using Perl or some other tool.
I have to disagree, at least on the BIOS front. BIOS is a mess, hard to code for, pragmatically impossible to patch (how many users will actually do the updates). BIOS is a 16 bit system... it _needed_ to go away. UEFI may not be perfect, and it may not be the best delivery, but BIOS simply can't support what systems provide these days. > 512 byte disk sectors, SSDs, massive ram, BIOS is crap at all of them. Sure you can shoehorn some support in, but it's still crap. Most systems have been on EFI much longer than most people realize (mid 90's for big systems, 2000 for consumer), and uEFI since 05.
Um... I believe the NSA is rather good at this. (I'm being serious) Maybe they can redeem themselves and put some of that internal cloud capability they have up for general government usage? They have the following skills/assets already in-house: * Security * Archiving * Indexing * Infrastructure * Scalability * Tons of other crap.
I'll give bonus points for re-using the existing equipment and drop table-ing the meta data they have on US citizens.
Add to that, if they're paying for your time while you're developing something, then there is legal precedent that they actually *own* what you developed.
My current company *finally* migrated our last project off VSS. I've used: ClearCase SVN Git Perforce VSS dated tarballs dated directories
So far my personal favorite is actually Perforce for massive codebases, and SVN for almost everything else. I have nothing against Git, but most of my crud is in SVN and I have no compelling case to change it.
Ever had this thing called eclipsed files with ClearCase? Ever received a huge E-mail with fifty "element"-lines as reply "can you give me your branch so that I can help out with your feature?". Ever didn't know what version of a file you were looking at because the config_spec has some magical order in that it processes said element lines (making me call ClearCase the SchrÃdingers Cat Management - you have to open the box to know if your code was dead or alive, and opening it kills it).
Ever saw compilation performance drop to 500% or 600% or more slower due to fstat being called on each and every header file in a preprocessed.cpp file's output over the network? (so, network latency is killing your compiler's speed). Ever had a SCM that required you to rewrite all your Makefiles in some absurdly stupid format so that some omake thing understands it?
Ever had to head time and time again that it's all your fault because "you don't use ClearCase right". While when you ask the ClearCase fanboys "so then how do I use it?" you basically get IBM this and IBM that and IBM is great and no answers.
I'm going to stop.. before I mental because of thinking about the horror I've been through.
Sorry. No keyboard. Poor guy.
Yes to most all of this. We had a *dedicated* CC management team of about 20 people. Seriously, their *entire* job was manage CC and related bullshit. So I didn't have to deal with the "you're not doing it right, but no help for you either." I got "you're not doing it right, use this tool we created that takes the input you gave and transmogrifies it to CC brainfuck".
Try migrating from CC to Perforce... Several hundred engineers have their workflow completely broken (yes P4 is *better* but the devil you know and all that). Productivity tanks for the first month as accidental overwrites of commits and reversions from merges and other wonderful shit hits all the fans...
This: I always provide my managers with confidence interval estimated times 50% 10 days (assumes *nothing* goes wrong, no interruptions, and high code reuse) 90% 15 days (assumes no catastrophic issues, no interruptions > 2 hours and only 5 of them, moderate code reuse) 100% 55 days (the wheels fell off, severe schedule impacts of interruptions non stop, no code reuse)
My boss laughed at my 100% estimate until it actually happened. A lead dev (who could be counted on for sound advice delivered in a belittling way) was struck down by lung cancer and ceased to exist. Another lead dev who was even brighter, and much nicer to work with was poached by a competitor, both within days of each other. The code was cutting all new territory in the system, so maybe 15% reuse? *and* some panicky manager started having $deity damned _daily_ meetings about it.
We almost missed my 100% date, made it by about 16 hours.
Slashdot Mirror
#define unless(x) if(!(x))
^how to *really* piss off the Perl hater in your C development team.
I think it was a PA swipe at Python (though one I happen to agree with).
That is my single biggest beef with Python.
Whitespace is *not* a character that the interpreter/compiler should care about other than the delimiters between tokens, and literal spaces in strings. (with due exception to the "whitespace" and brainfuck languages).
With just *how* entrenched some of the code is, that scenario is plausible (while still unlikely).
With modern programming languages -- I'll use Python as an example -- we use functions, objects, modules, and libraries
Who writes this shit?
Obviously, not a programmer.
Those who can, do. ...
Those who can't
you missed a spot: ... by using synergistic energies between stakeholders ... /*pukes*
Well, to be fair you can, even with python, or perl.
write script that accepts textfile of op codes, convert opcodes to asm using pack();
write to file in binmode.
Simple! (stupid for sure, but simple).
I guess that's really a compiler more than direct...
make your compiler able to convert python to asm. there. stupider and still simple.
TL;DR of above:
I *dislike* Python (I'm a Perl guy, I want my curlies and semis damnit...). Sure I could contrive to write a driver in a scripting language, but why? If I'm mucking about with IOCTLS I'm in C/C++. If I'm scanning my C driver code for issues, LOC counts, unsafe operators, etc. at a level deeper than the compiler then I'm using Perl or some other tool.
Right language for the job and all that.
I have to disagree, at least on the BIOS front.
BIOS is a mess, hard to code for, pragmatically impossible to patch (how many users will actually do the updates).
BIOS is a 16 bit system... it _needed_ to go away.
UEFI may not be perfect, and it may not be the best delivery, but BIOS simply can't support what systems provide these days. > 512 byte disk sectors, SSDs, massive ram, BIOS is crap at all of them. Sure you can shoehorn some support in, but it's still crap. Most systems have been on EFI much longer than most people realize (mid 90's for big systems, 2000 for consumer), and uEFI since 05.
NT4.0sp6a might be more accurate :/
Um...
I believe the NSA is rather good at this. (I'm being serious)
Maybe they can redeem themselves and put some of that internal cloud capability they have up for general government usage?
They have the following skills/assets already in-house:
* Security
* Archiving
* Indexing
* Infrastructure
* Scalability
* Tons of other crap.
I'll give bonus points for re-using the existing equipment and drop table-ing the meta data they have on US citizens.
Flight engineer.
Sounds like my ex wife.
Points at the Sep MOU when she wants something, totally ignores it otherwise.
I know it doesn't account for all of it, but I've lost many female co-workers to motherhood and their decision to stay at home with their children.
I actually line-itemed that out in my offer letter and got no pushback. (the developed on my own time, not on company owned equipment part).
you are a *rare* employer.
My hat's off to you for being transparent on your expectations. I hope your business flourishes.
/topic
It is *that* straightforward.
Add to that, if they're paying for your time while you're developing something, then there is legal precedent that they actually *own* what you developed.
My current company *finally* migrated our last project off VSS.
I've used:
ClearCase
SVN
Git
Perforce
VSS
dated tarballs
dated directories
So far my personal favorite is actually Perforce for massive codebases, and SVN for almost everything else.
I have nothing against Git, but most of my crud is in SVN and I have no compelling case to change it.
Makes sense to me...
But only because I've dealt with the mindfuck of ClearCase.
I'm not entirely sure that Visual Source Safe is worse in fact...
Ever had this thing called eclipsed files with ClearCase? Ever received a huge E-mail with fifty "element"-lines as reply "can you give me your branch so that I can help out with your feature?". Ever didn't know what version of a file you were looking at because the config_spec has some magical order in that it processes said element lines (making me call ClearCase the SchrÃdingers Cat Management - you have to open the box to know if your code was dead or alive, and opening it kills it).
Ever saw compilation performance drop to 500% or 600% or more slower due to fstat being called on each and every header file in a preprocessed .cpp file's output over the network? (so, network latency is killing your compiler's speed). Ever had a SCM that required you to rewrite all your Makefiles in some absurdly stupid format so that some omake thing understands it?
Ever had to head time and time again that it's all your fault because "you don't use ClearCase right". While when you ask the ClearCase fanboys "so then how do I use it?" you basically get IBM this and IBM that and IBM is great and no answers.
I'm going to stop.. before I mental because of thinking about the horror I've been through.
Sorry. No keyboard. Poor guy.
Yes to most all of this.
We had a *dedicated* CC management team of about 20 people.
Seriously, their *entire* job was manage CC and related bullshit.
So I didn't have to deal with the "you're not doing it right, but no help for you either." I got "you're not doing it right, use this tool we created that takes the input you gave and transmogrifies it to CC brainfuck".
Well done with the Musicman reference!
Sir!
Immagine how much you could sell memberships ar Luna-Lago for!
nevermind this:
future devices would be built around different chips that would also be able to encrypt messages as they travelled.
So it's a fail right off the bat if it doesn't encrypt the mail in the first place.
Try migrating from CC to Perforce...
Several hundred engineers have their workflow completely broken (yes P4 is *better* but the devil you know and all that). Productivity tanks for the first month as accidental overwrites of commits and reversions from merges and other wonderful shit hits all the fans...
This:
I always provide my managers with confidence interval estimated times
50% 10 days (assumes *nothing* goes wrong, no interruptions, and high code reuse)
90% 15 days (assumes no catastrophic issues, no interruptions > 2 hours and only 5 of them, moderate code reuse)
100% 55 days (the wheels fell off, severe schedule impacts of interruptions non stop, no code reuse)
My boss laughed at my 100% estimate until it actually happened.
A lead dev (who could be counted on for sound advice delivered in a belittling way) was struck down by lung cancer and ceased to exist. Another lead dev who was even brighter, and much nicer to work with was poached by a competitor, both within days of each other. The code was cutting all new territory in the system, so maybe 15% reuse? *and* some panicky manager started having $deity damned _daily_ meetings about it.
We almost missed my 100% date, made it by about 16 hours.
Nah, just sell those glasses frames that confused facial recognition systems:
http://www.theverge.com/2016/1...
*everyone* is the Queen of England.