Perl has things that no other (typical) language has. That's what makes it ridiculously difficult for programmers coming from C: hidden variables, context-sensitive variables, native regular expressions, and lists -- no C-style language has lists; there's no concept of a function that returns multiple objects in C; and there certainly isn't any concept of a function that knows how its return will be cast by the caller.
Glad your way passifies you. I've been profitting for two decades now. I'm telling you that I've made over a million dollars doing it this way. You can go about it any way you choose. I'm saying no IDE, no debugger, no delays, no learning, no time wasted means no complexity. It's just me and the code and the output. I'm saying that works best.
I'm saying that works best six months later when the client wants a new feature. I'm saying that works best a year later when I'm with a client, in a field, with a compound bow in my left hand and an arrow tail in my right and she asks me how much a new feature will cost and how long it'll take to deliver and I can give her an answer before my arrow hits the ground nowhere near the target.
Again, you can do things any way you like -- or have been taught. I've never listened to anyone who's attempted to teach me anything in this industry. You and I are very different.
You and I can't live together. I'll never sleep with you. I'll never share a meal with you. You and I, we're done.
I've spent 3 decades avoiding IDEs. From LOGO at age 5, through my own business to this day. No IDEs, ever. LOGO, basic, C, C++, C++/DirectX, Lotus Notes, Perl, HTML, Javascript, PHP, HTA, CSS, Pipelines. I've used notepad, and now ultraedit for syntax highlighting, and proper find tools, and integrated ftp, but that's about it.
I'll never choose to waste my time learning an IDE -- which amounts to someone else's idea of how I should use a given language. I'll write my own, thank you very much.
only if you've never learned how to debug javascript. If you're using debugging tools, then yes, 17 hours is about right. If you've been debugging interpreted languages for decades, then it's no big deal.
Just keep running it as you code -- every time you type a semi-colon, hit F5. When it doesn't do what you expect, the problem is in the last line that you typed. There's no compiling, and there's no linking, and there's no delay. In an hour of coding, you should be executing it well over 30 times. Adapt your coding style to sequence things atomically, and you won't have any problems.
Until you type "tmep" instead of "temp" and it takes you a day to figure it out because javascript does very stupid things with variable scope that no other language would consider legal in any way -- like variables being in-scope before the line declaring them.
read the original post again. he's looking for one-off tools. 17% of javascript is plenty for 70% of tools. the HTA (JScript) will provide the other 30%, no problem.
javascript takes about 17 minutes to learn -- same basic syntax as C, plus a document object model -- a big hash structure full of values defining the html. Wrap it in an HTA, and you've got an executable with full access to the entire machine (windows only, of course), including the file system, ODBC connectivity, system ports, et cetera.
I'll always prefer perl for data processing, but you don't want to learn perl. That's a very very steep learning curve -- because that's the point.
But javascript is dead-simple. You can make a quick-tool HTA in seconds. Being HTML, the GUI comes for free. It's the same html and javascript for any mobile or web anything.
Look, it's very simple. If the animal alters the temperature of its own blood, to be different than the environmental temperature, by anything more significant than standard locomotion (we won't count walking to the toilet, but we will count routinely running on a treadmill), then the animal is warm blooded.
I don't care if it's controlled to a constant temperature, and I don't care if it's through metabolic activity, muscular activity, solar receptors, or nuclear fission reactors.
Case in points: I am warm blooded, even though my blood temp drops by as many as 2C in the cold. I am also warm blooded even when my blood is colder than the environment in the summer. Warm has never meant warmer. Warm has never meant constant. Warm has never meant controlled. Warm has only ever meant changed.
Everything else is simply the same set of lies, twisted and contorted to over-simplify an observation or to over-fit a given hypothesis.
No one has ever thought that dinosaur blood was always the same temperature as the environment. And that doesn't make them cold blooded. And it doesn't make them warm blooded. And it doesn't make them neither. And it doesn't make them both. It mades you argumentative for absolutely no reason.
Recipes require technical skill to follow. Words matter. Mincing is different than chopping. Internal temperatures, resting, and precise amounts are all very familiar concepts. Recipes are documentation. Anyone who can't cook simply can't figure out how to follow very precise directions in-sequence.
In my kitchen, I re-write/re-format recipes into documentation -- I lay things out in a manner consistent with technical writing, which makes things oh so much easier and faster to follow. None of these long-winded, yet abbreviated-to-shit method paragraphs, and long-listed ingredient columns which seven different units of measure. The funny part is that even though my programming is rarely object-oriented -- I simply don't care for it -- my recipes are almost always object-oriented! Well, bowl-oriented. Go figure.
If everything that affects anyone is your problem, then you've got about a billion problems to deal with. That's not feasible. So that's just plain stupid.
This all falls well within the not-my-problem camp. There are problems in this world that are not mine, nor are they not my responsibility to solve. There are plenty of women alive to solve them. And if 1 in 6 have this problem, then there are literally hundreds of millions to solve them. Why the hell do you need me to do anything? If 1 in 6 women is too lazy to do anything about it, then really it doesn't fall on me to solve the problem for them.
I've got problems of my own, and I don't ask 1 in 6 women to solve them for me. I think they are more than capable of solving this one for themselves.
Last I checked, male university students don't get free escorts home at night, yet female university students around here do.
Me solving their problems would go against everything they fought for. I supported women's equal rights. Let them enjoy their equal rights.
They have the equal right to solve their own problems. I sure as hell won't fight their battles for them.
I've avoided tablets, laptops, and smartphones until now, purely because I can't possibly get any work safely done on any of them, and I've got zero interest in infotainment as recreation. I don't need to watch youtube videos of concerts -- I just go to the concerts.
But this is actually suitable as a minimal desk when I'm on vacation -- which means that I can stay on vacation longer with less cover. All I need is a car adapter and I'll be done.
Look at me, I'm finally buying a portable computer. Wow, 2014.
"advertising" used to be about "advertising" the existence of a product or service. After all, how would I know that something's for sale without it being advertised?
But really, I think we've fallen far far away from that. I know that laundry detergent exists. I know where to find laundry detergent too. If you want to advertise your detergent in the aisle at the store, that'd be great. But I really don't need you to yell your detergent brand at me when I'm at home. I'm not going to suddenly get up and go buy even more detergent.
I'm not going to have ads on my fridge. Aside from buying commercial-grade fridges that don't even have water dispensers, let alone lcd screens, I do buy my fair share of duct tape -- for which I've never seen an ad. Actually, I buy Gorilla tape -- for which I've also never seen an ad. Both tapes do a great job of covering up LCD screens.
But more than anything, this is what confuses me. I'm not going to spend any more money. I simply don't have any more money to spend. It's not like more ads will convince me to buy more of anything. So aside from shifting my brand loyalty from one brand of printer paper to another, I really just don't see the point.
No, you're absolutely right. I meant that in more of the current technical application for brakes in racecars and such. Personally, and professionally, I love aluminum. And because it's a lot more sturdy, it holds a structural shape much better than steel does.
Though it does have some properties that just totally killed it in one of my projects. It shields radiation so well that I couldn't get a wi-fi signal through it at all. Steel didn't have that issue.
But by far, the funniest part was when I grabbed a steel nibbler and tried to use it on aluminum sheet. I've never seen a professional tool break so easily in all my life. I was bewildered.
I think you'd have a hard time keeping the lead there. Lead's pretty soft and melts easily, if I remember correctly. So it'd probably fall off faster than it would do anything else.
I find it interesting to note that all of your examples are of structural, non-frictional components, which doesn't really apply here. I'd have argued that while most metals are readily engineered for differing properties, 90% of those efforts fail miserably in frictional, high-heat, high-wear applications, where the base material undergoes chemically-significant physical forces -- like friction.
In any event, my comments were not intended to describe all steel and all carbon. Instead they were meant to describe the steel and carbon being used in the report. I don't really care about any others in this thread.
On the other hand, if you'd like to get into my personal experiences with aluminum on hang gliders, or my professional expreiences with aluminums and steels in commercial environments, or my pseudo-professional experiences with aluminums, steels, and irons in kitchen environments, my knowledge is narrow but deep in the first, broad and deep in the second, broad and shallow in the third.
Umm, whatever your industry's definition of "strength", you'll find that it morphs across the three disciplines involved here. You'll also note that your own industry's definition of "strength" doesn't distinguish between various directions. So if I were to say that steel is stronger laterally, vs carbon's strength longitudinally, I'd still be within your industry.
Your industry also flexes in terms of the definition of the term "failure under load". Failure in some instances means breaking under the stress applied, but in others in means breaking as a result of the stress applied. In this case, we're talking about a spinning disk. If the material can withstand the load without the spinning, but then breaks due to the spinning, the term "strength" either does or does not cover the actual environment being discussed.
All of that aside, you'll note that this is not a materials sciences web-site, nor is it a theorhetical sciences journal. It is a site specifically for autistic yaps who make billions of dollars by transforming complicated depths into familiar fundamentals.
I think people forget that "stronger" is meaningless. In the case of steel vs carbon, carbon is going to be stronger for a given weight, but that just makes the word "stronger" even more meaningless.
Steel usually wins out against most materials when it comes to survival. Steel bends, and bends back. Just about everything else loses by being brittle. Aluminum is the best example, being about three times lighter, but incredibly brittle. Carbon is also very brittle, just at the microscopic level. It'll fray, and slowly degrade until it comes a part -- like most fabrics.
Steel deforms, and then melts back together and deforms again. In order for friction to destroy steel, it needs to actually wear it away one particle at a time. Being so much heavier/denser, there are that many more particles to wear away. That's the win.
Why are people surprised when mass wins in a mass-bound effort? The challenge here is to get a heavy car to go really fast, and to then slow it down. That's always been a mass vs mass game. More mass always wins.
My question remains: if the carbon solution were as heavy as the steel solution, would it survive? But we all know that you can't cram that much carbon fibre into the same style of braking system.
Electric is simply to inefficient to collect-produce-transport-distribute-convert-convert-convert, and in the end it necessitates highly active infrastructure. Perhaps in the heart of a metropolis that can work, but it might as well power bicycles in that environment.
Hydrogen, as many have said, sucks in the practical convenience of transport. Everything's pressurized, nothing's stable, and it's constantly trying to get away.
I'm a Mazda fan. I like the idea of making the car more and more efficient to the point where in can run on less and less gasolene. At some point, it'll be so efficient that it won't need such a purely refined fuel, and could wind up burning anything -- like orange juice.
With less-refined fuels be required, there are oh-so-many-more options available, including solid fuel components.
So that's my distant-future foresight: two cubes that ultimately get crushed/melted/dissolved/vapourized into something that combusts. Transporting stable and solid fuels in incredibly easy; there's effectively no direct loss during transport; and there's zero active infrastructure to maintain. If it's stable enough, you could leave giant piles of it by the road, and just run a vending box, like the old curb-side newspaper boxes.
Yeah, all of that is known as growing up. If you've made it to forty, and can't govern yourself, then you've simply failed as a productive part of society. You can't possibly keep up with a 20-year old on their strengths, and you're ignoring all of the strengths of being a 40-year old. I'm certainly not going to hire a 40-year old to work under me. I'm 35. But I won't contract a 20-year old as a supplier either. Expertise, experience, and accountability as key things that come with calendars. Ignoring your own benefits is just idiotic.
And besides, according to you, 99.99% of people fall into your incapable categoy. Bullshit.
But hey, keep importing more H1-B foreign workers for the jobs, keep paying welfare to your unemployed, keep screwing yourselves out of every bit of your lifestyle. It all works in my favour. I wind up benefiting from all of it.
You're forty. Stop relying on others to give you a job. Start creating jobs of your own. By now you ought to have matured enough to take your own risks, guarantee your own work, and stop being a drain on the job market.
Do you plan to work for a boss for the rest of your life? What a loser. Can't sign your own paychecks? Can convince clients that you're worth any money on your own? Does your mommy still hold your hand too?
Seriously, it's time to grow up and make a job of your own.
Slashdot Mirror
Perl has things that no other (typical) language has. That's what makes it ridiculously difficult for programmers coming from C: hidden variables, context-sensitive variables, native regular expressions, and lists -- no C-style language has lists; there's no concept of a function that returns multiple objects in C; and there certainly isn't any concept of a function that knows how its return will be cast by the caller.
Glad your way passifies you. I've been profitting for two decades now. I'm telling you that I've made over a million dollars doing it this way. You can go about it any way you choose. I'm saying no IDE, no debugger, no delays, no learning, no time wasted means no complexity. It's just me and the code and the output. I'm saying that works best.
I'm saying that works best six months later when the client wants a new feature. I'm saying that works best a year later when I'm with a client, in a field, with a compound bow in my left hand and an arrow tail in my right and she asks me how much a new feature will cost and how long it'll take to deliver and I can give her an answer before my arrow hits the ground nowhere near the target.
Again, you can do things any way you like -- or have been taught. I've never listened to anyone who's attempted to teach me anything in this industry. You and I are very different.
You and I can't live together. I'll never sleep with you. I'll never share a meal with you. You and I, we're done.
I've spent 3 decades avoiding IDEs. From LOGO at age 5, through my own business to this day. No IDEs, ever. LOGO, basic, C, C++, C++/DirectX, Lotus Notes, Perl, HTML, Javascript, PHP, HTA, CSS, Pipelines. I've used notepad, and now ultraedit for syntax highlighting, and proper find tools, and integrated ftp, but that's about it.
I'll never choose to waste my time learning an IDE -- which amounts to someone else's idea of how I should use a given language. I'll write my own, thank you very much.
only if you've never learned how to debug javascript. If you're using debugging tools, then yes, 17 hours is about right. If you've been debugging interpreted languages for decades, then it's no big deal.
Just keep running it as you code -- every time you type a semi-colon, hit F5. When it doesn't do what you expect, the problem is in the last line that you typed. There's no compiling, and there's no linking, and there's no delay. In an hour of coding, you should be executing it well over 30 times. Adapt your coding style to sequence things atomically, and you won't have any problems.
Until you type "tmep" instead of "temp" and it takes you a day to figure it out because javascript does very stupid things with variable scope that no other language would consider legal in any way -- like variables being in-scope before the line declaring them.
the former for the original poster's skills-set, the latter for mine. I've got more equipment, and decades with perl.
read the original post again. he's looking for one-off tools. 17% of javascript is plenty for 70% of tools. the HTA (JScript) will provide the other 30%, no problem.
javascript takes about 17 minutes to learn -- same basic syntax as C, plus a document object model -- a big hash structure full of values defining the html. Wrap it in an HTA, and you've got an executable with full access to the entire machine (windows only, of course), including the file system, ODBC connectivity, system ports, et cetera.
I'll always prefer perl for data processing, but you don't want to learn perl. That's a very very steep learning curve -- because that's the point.
But javascript is dead-simple. You can make a quick-tool HTA in seconds. Being HTML, the GUI comes for free. It's the same html and javascript for any mobile or web anything.
Look, it's very simple. If the animal alters the temperature of its own blood, to be different than the environmental temperature, by anything more significant than standard locomotion (we won't count walking to the toilet, but we will count routinely running on a treadmill), then the animal is warm blooded.
I don't care if it's controlled to a constant temperature, and I don't care if it's through metabolic activity, muscular activity, solar receptors, or nuclear fission reactors.
Case in points: I am warm blooded, even though my blood temp drops by as many as 2C in the cold. I am also warm blooded even when my blood is colder than the environment in the summer. Warm has never meant warmer. Warm has never meant constant. Warm has never meant controlled. Warm has only ever meant changed.
Everything else is simply the same set of lies, twisted and contorted to over-simplify an observation or to over-fit a given hypothesis.
No one has ever thought that dinosaur blood was always the same temperature as the environment. And that doesn't make them cold blooded. And it doesn't make them warm blooded. And it doesn't make them neither. And it doesn't make them both. It mades you argumentative for absolutely no reason.
Recipes require technical skill to follow. Words matter. Mincing is different than chopping. Internal temperatures, resting, and precise amounts are all very familiar concepts. Recipes are documentation. Anyone who can't cook simply can't figure out how to follow very precise directions in-sequence.
In my kitchen, I re-write/re-format recipes into documentation -- I lay things out in a manner consistent with technical writing, which makes things oh so much easier and faster to follow. None of these long-winded, yet abbreviated-to-shit method paragraphs, and long-listed ingredient columns which seven different units of measure. The funny part is that even though my programming is rarely object-oriented -- I simply don't care for it -- my recipes are almost always object-oriented! Well, bowl-oriented. Go figure.
...There's just no way that this holds up. Watch and see.
If everything that affects anyone is your problem, then you've got about a billion problems to deal with. That's not feasible. So that's just plain stupid.
This all falls well within the not-my-problem camp. There are problems in this world that are not mine, nor are they not my responsibility to solve. There are plenty of women alive to solve them. And if 1 in 6 have this problem, then there are literally hundreds of millions to solve them. Why the hell do you need me to do anything? If 1 in 6 women is too lazy to do anything about it, then really it doesn't fall on me to solve the problem for them.
I've got problems of my own, and I don't ask 1 in 6 women to solve them for me. I think they are more than capable of solving this one for themselves.
Last I checked, male university students don't get free escorts home at night, yet female university students around here do.
Me solving their problems would go against everything they fought for. I supported women's equal rights. Let them enjoy their equal rights.
They have the equal right to solve their own problems. I sure as hell won't fight their battles for them.
I'd love a definition of fresh that doesn't allow for six months of warehousing before I eat it, thank you very much.
...destroying their ability to learn *without them*.
Whether or not that's a bad thing is a totally different discussion. Do you think the future of learning is with or without computers?
Welcome to focus and opportunity cost.
I've avoided tablets, laptops, and smartphones until now, purely because I can't possibly get any work safely done on any of them, and I've got zero interest in infotainment as recreation. I don't need to watch youtube videos of concerts -- I just go to the concerts.
But this is actually suitable as a minimal desk when I'm on vacation -- which means that I can stay on vacation longer with less cover. All I need is a car adapter and I'll be done.
Look at me, I'm finally buying a portable computer. Wow, 2014.
"advertising" used to be about "advertising" the existence of a product or service. After all, how would I know that something's for sale without it being advertised?
But really, I think we've fallen far far away from that. I know that laundry detergent exists. I know where to find laundry detergent too. If you want to advertise your detergent in the aisle at the store, that'd be great. But I really don't need you to yell your detergent brand at me when I'm at home. I'm not going to suddenly get up and go buy even more detergent.
I'm not going to have ads on my fridge. Aside from buying commercial-grade fridges that don't even have water dispensers, let alone lcd screens, I do buy my fair share of duct tape -- for which I've never seen an ad. Actually, I buy Gorilla tape -- for which I've also never seen an ad. Both tapes do a great job of covering up LCD screens.
But more than anything, this is what confuses me. I'm not going to spend any more money. I simply don't have any more money to spend. It's not like more ads will convince me to buy more of anything. So aside from shifting my brand loyalty from one brand of printer paper to another, I really just don't see the point.
No, you're absolutely right. I meant that in more of the current technical application for brakes in racecars and such. Personally, and professionally, I love aluminum. And because it's a lot more sturdy, it holds a structural shape much better than steel does.
Though it does have some properties that just totally killed it in one of my projects. It shields radiation so well that I couldn't get a wi-fi signal through it at all. Steel didn't have that issue.
But by far, the funniest part was when I grabbed a steel nibbler and tried to use it on aluminum sheet. I've never seen a professional tool break so easily in all my life. I was bewildered.
I think you'd have a hard time keeping the lead there. Lead's pretty soft and melts easily, if I remember correctly. So it'd probably fall off faster than it would do anything else.
I find it interesting to note that all of your examples are of structural, non-frictional components, which doesn't really apply here. I'd have argued that while most metals are readily engineered for differing properties, 90% of those efforts fail miserably in frictional, high-heat, high-wear applications, where the base material undergoes chemically-significant physical forces -- like friction.
In any event, my comments were not intended to describe all steel and all carbon. Instead they were meant to describe the steel and carbon being used in the report. I don't really care about any others in this thread.
On the other hand, if you'd like to get into my personal experiences with aluminum on hang gliders, or my professional expreiences with aluminums and steels in commercial environments, or my pseudo-professional experiences with aluminums, steels, and irons in kitchen environments, my knowledge is narrow but deep in the first, broad and deep in the second, broad and shallow in the third.
oops, my mistake. I didn't mean to type fibre. Thanks!
Umm, whatever your industry's definition of "strength", you'll find that it morphs across the three disciplines involved here. You'll also note that your own industry's definition of "strength" doesn't distinguish between various directions. So if I were to say that steel is stronger laterally, vs carbon's strength longitudinally, I'd still be within your industry.
Your industry also flexes in terms of the definition of the term "failure under load". Failure in some instances means breaking under the stress applied, but in others in means breaking as a result of the stress applied. In this case, we're talking about a spinning disk. If the material can withstand the load without the spinning, but then breaks due to the spinning, the term "strength" either does or does not cover the actual environment being discussed.
All of that aside, you'll note that this is not a materials sciences web-site, nor is it a theorhetical sciences journal. It is a site specifically for autistic yaps who make billions of dollars by transforming complicated depths into familiar fundamentals.
So why are you here?
I think people forget that "stronger" is meaningless. In the case of steel vs carbon, carbon is going to be stronger for a given weight, but that just makes the word "stronger" even more meaningless.
Steel usually wins out against most materials when it comes to survival. Steel bends, and bends back. Just about everything else loses by being brittle. Aluminum is the best example, being about three times lighter, but incredibly brittle. Carbon is also very brittle, just at the microscopic level. It'll fray, and slowly degrade until it comes a part -- like most fabrics.
Steel deforms, and then melts back together and deforms again. In order for friction to destroy steel, it needs to actually wear it away one particle at a time. Being so much heavier/denser, there are that many more particles to wear away. That's the win.
Why are people surprised when mass wins in a mass-bound effort? The challenge here is to get a heavy car to go really fast, and to then slow it down. That's always been a mass vs mass game. More mass always wins.
My question remains: if the carbon solution were as heavy as the steel solution, would it survive? But we all know that you can't cram that much carbon fibre into the same style of braking system.
Electric is simply to inefficient to collect-produce-transport-distribute-convert-convert-convert, and in the end it necessitates highly active infrastructure. Perhaps in the heart of a metropolis that can work, but it might as well power bicycles in that environment.
Hydrogen, as many have said, sucks in the practical convenience of transport. Everything's pressurized, nothing's stable, and it's constantly trying to get away.
I'm a Mazda fan. I like the idea of making the car more and more efficient to the point where in can run on less and less gasolene. At some point, it'll be so efficient that it won't need such a purely refined fuel, and could wind up burning anything -- like orange juice.
With less-refined fuels be required, there are oh-so-many-more options available, including solid fuel components.
So that's my distant-future foresight: two cubes that ultimately get crushed/melted/dissolved/vapourized into something that combusts. Transporting stable and solid fuels in incredibly easy; there's effectively no direct loss during transport; and there's zero active infrastructure to maintain. If it's stable enough, you could leave giant piles of it by the road, and just run a vending box, like the old curb-side newspaper boxes.
Yeah, all of that is known as growing up. If you've made it to forty, and can't govern yourself, then you've simply failed as a productive part of society. You can't possibly keep up with a 20-year old on their strengths, and you're ignoring all of the strengths of being a 40-year old. I'm certainly not going to hire a 40-year old to work under me. I'm 35. But I won't contract a 20-year old as a supplier either. Expertise, experience, and accountability as key things that come with calendars. Ignoring your own benefits is just idiotic.
And besides, according to you, 99.99% of people fall into your incapable categoy. Bullshit.
But hey, keep importing more H1-B foreign workers for the jobs, keep paying welfare to your unemployed, keep screwing yourselves out of every bit of your lifestyle. It all works in my favour. I wind up benefiting from all of it.
You're forty. Stop relying on others to give you a job. Start creating jobs of your own. By now you ought to have matured enough to take your own risks, guarantee your own work, and stop being a drain on the job market.
Do you plan to work for a boss for the rest of your life? What a loser. Can't sign your own paychecks? Can convince clients that you're worth any money on your own? Does your mommy still hold your hand too?
Seriously, it's time to grow up and make a job of your own.