I keep all the devices segregated, no sharing, no sync, no cloud, no BS. When I'm at home I don't see anything about work, and people who do want to see their work stuff at home need to learn to cut that umbilical cord.
If there's one reason why Firefox is declining it is because they're pissing off their customers with the update speeds. If there's a second reason, it's because they copy Chrome slavishly, as if they can't start developing any features until they see it somewhere else first. I still use it though because I am still allowed to turn off features and use the very few plugins I want.
That's why they should clean up early, so that early on they know their business plan won't work. If they wait until there is actually significant polution, then they've been given a free pass. (ok, they may go bankrupt but the CEO is still retiring to a golden palace)
There are a couple things you want in a beginner's language, and simplicity is one, but enforcement of good style is also vital. Consider BASIC, it was very simple but it was a terrible language for beginners as it encouraged really horrible programming practices. When assisting in a beginning programming class one of the hardest things to do (in 1983 era) was to break BASIC programmers out of their bad habits. I work with a lot of self-taught programmers (EE orientation) who like to stick state into global variables, randomly scatter around type casts until the compiler stops complaining, and so forth.
Python works in the first sense. It's a bit weaker in the second sense given that type declarations don't exist. As a scripting language you don't find out errors until you run the code, there's no compile time validation or analysis that points out errors which makes it even more vital to very thorough code coverage testing. Ie, variable "x" was a string, but you just assigned an integer to it, how does the system know it's an error versus the programmer intentionally wanted implicit conversions done? In that sense I'd put Java above Python for beginners, despite Python having the simpler syntax and rules.
It's perspective though. For me, I do lower level languages and experience shows that it is easier for someone who knows lower level languages to learn high level scripting languages than vice versa. Knowing the relationship of what the program does and how it affects the machine underneath is important. In scripting languages it's normal to be a bit loose and free with the rules, the goal is to get 'er done. For low level languages the goal is often correctness, reliability, and performance.
Best class I think I had at university of Comparison of Programming Languages. Good at a theoretical level, but also because homework involved using other languages with wildly different approaches. Ada, Lisp, Prolog, etc. Such stuff gets you out of the mindset that programming is just doing sequential operations, and that there is more than one way to structure code and data.
This was for a device not the web, and I needed the binary data. It was only used as key/value holders, no such thing as URI or MIME exists on the system. There was no need for JSON but someone felt it was more "standard" than a different protocol we had been using. Thy syntax was the only specification I could find at the time, no description of how to specify something other than numbers or strings. On hindsight I probably could have just looked at some Javascript documentation.
It's not that Pascal is less complex that makes it good, another important fact is that it enforces good programming. We taught it to freshmen decades ago and those who already knew some BASIC wo proclaimed loudly that they were already good programmers would bitch and whine about how hard all the structured code was and why did they had to declare variables before using them.
But they're going to need the people with a career/profession/calling somewhere in the mix. Sure, the coders on the digital assembly line don't need to be the best, but you do need someone out there who's got more experience and education to design the system. Except with apps of course, apps are generally standalone pieces of fluff for the most part, no one cares about maintainability, performance, or reliability, so you can get an intern for that or else outsource it.
I disagree a bit here. The biggest failing I see in computer science is in trying to teach the popular languages like it was a mere two year trade school. Good programmers can learn any language, they don't need the university to teach it. Of course, the most popular languages may become the ones that are taught in higher level courses, that's just natural. But when a curriculum is derived around teaching what's popular then it loses a lot of academic value. A beginner's language while learning however may not necessarily be the most popular language. I started in Pascal, and it was great for teaching compared the other other popular languages because it enforced structured programming and strong typing from day one.
In my 30+ years of programming, the worst programmers who caused the most damage were the ones who thought they were hot shit superstar programmers, despite making the same boneheaded errors all the time. Generally they wanted to work solo and never as a team.
They usually got filtered out as freshmen when I was in college, in the intro to programming class. That class was never going to teach you enough to get a decent job in programming, and was not intended to do so anyways. A few students felt compelled to be in the courses though, because their parents had picked out the career for them.
Yes, I found that when I needed to do JSON parsing that it was vaguely defined. You need to know other stuff before you can proceed, which is why I really hesitate to call it a standard because so much is missing in the very short specification I read. The specification does say reasonably clearly how to parse, but not how to interpret the data that gets parsed. The stuff you need to know is that this is Javascript code compatible, thus the data types are the same as they are in Javascript, and strings can be used to encode binary data using base64, etc. Also imagine that there is an implicit "{" and "}" surrounding all of it.
JSON is a lot smaller. No schemas, properties, etc. It's just data definition and nothing more. Store your data in a bulky format, read it back again, send it over the network in a bulky but device independent manner, etc.
The reason for its existence is precisely because it is Javascript subset. No one invented a new library for it originally, it was just snippets of Javascript data declarations that someone used on their website.
Not for XML, but for JSON, I wrote my own library. Had to, one did not exist for the device that met the requirements. Not everything is a PC. And if you do want proper libraries, they will still disagree with each other! One problem I have seen more than once is the assumption that a library is correct merely because it's a library from a third party (as in my fellow coworkers are morons but anyone outside the building clearly has a comprehensive understanding of all the standards and was given enough time to complete the feature without ever feeling rushed).
JSON as a standard is very weak. It's hard to find a well defined specification suitable for implementing. There are a lot of assumptions made. Ie, how do you store binary data? Normally base64 but nothing requires this or specifies what base64 is and how it must be represented and what to do with the leftover odd bytes at the end. But everyone sort of knows as vague tribal knowledge what to do (do what Javascript does, do it the same way Python library does it, etc). It's a simple format, it has much going for it, but it's not formally specified.
For a while, all the cool people stopped wearing them, looking at you like a hopelessy out of touch dinosaur if you kept a watch. Then very quickly that reversed itself, now all the cool people and hipsters wear smart watches, Fitbits that tell time, and other time telling devices worn on the wrist. AND normal old fashioned analog watches are appearing on peopel's wrists. The lack of wrist watches was one of the shortest lived fashion trends that I can remember.
In the US this is not exactly true, the government is not above the law. The executive does not make the laws, it only enforces them. Even though congress makes the laws it changes its mind very often. The courts can also step in and declare the a law conflicts with other laws. Presidents often discover that things aren't so easy to implement as they think they are before coming to office.
And yet winning lawsuits against the government has happened in the past. The US government is not unified, the courts, legislature, and executive do not agree with each other. We have had overreaching intelligence activities slapped down before by congress and the courts.
Political parties are all about, at their heart, marketing. The only difference from your average telemarketer is the lack of quality of the product they are selling.
Not true. I get voicemail from family all the time. Since it's on the phone they assume I will see it eventually. The phone calls don't get through because I won't answer the phone all the time, I may be in meetings, drivings, at the store, etc. That's the whole purpose of voice mail so that the phone stops becoming your master and demanding that you respond NOW or else!
Deportations under Obama administration were higher than under any other president, it's really a stretch for some people to call him soft on illegal immigration given the numbers.
Nothing above the law about sanctuary cities. The federal government can request assistance with immigration enforcement but the local governments are not compelled to cooperate. There is no law that says they must assist the INS on demand.
INS claims (falsely) that they're only focusing on undocumented immigrants if they have committed serious crimes, and in such cases even sanctuary cities cooperate and turn the prisoners over. The case that riled so many against sanctuary cities when an illegal immigrant killed someone in San Francisco, there was no active warrant for the killer and there was no reason to continue detaining him. ICE requested he be detained but there was no legal basis for further detaining. The killer had no history of violent crimes, his deporations were due to drug laws and attempting re-entry to the US.
Now would it have been above the law to detain a person when no charges had been filed, no warrant or evidence presented, but merely because a federal agent asked for this?
Doesn't matter, Trump doesn't write the proposed budget personally. Hopefully he at least reviews the budget, but he's certainly not sitting there with a calculator and green eyeshades.
Slashdot Mirror
I keep all the devices segregated, no sharing, no sync, no cloud, no BS. When I'm at home I don't see anything about work, and people who do want to see their work stuff at home need to learn to cut that umbilical cord.
If there's one reason why Firefox is declining it is because they're pissing off their customers with the update speeds. If there's a second reason, it's because they copy Chrome slavishly, as if they can't start developing any features until they see it somewhere else first. I still use it though because I am still allowed to turn off features and use the very few plugins I want.
That's why they should clean up early, so that early on they know their business plan won't work. If they wait until there is actually significant polution, then they've been given a free pass. (ok, they may go bankrupt but the CEO is still retiring to a golden palace)
There are a couple things you want in a beginner's language, and simplicity is one, but enforcement of good style is also vital. Consider BASIC, it was very simple but it was a terrible language for beginners as it encouraged really horrible programming practices. When assisting in a beginning programming class one of the hardest things to do (in 1983 era) was to break BASIC programmers out of their bad habits. I work with a lot of self-taught programmers (EE orientation) who like to stick state into global variables, randomly scatter around type casts until the compiler stops complaining, and so forth.
Python works in the first sense. It's a bit weaker in the second sense given that type declarations don't exist. As a scripting language you don't find out errors until you run the code, there's no compile time validation or analysis that points out errors which makes it even more vital to very thorough code coverage testing. Ie, variable "x" was a string, but you just assigned an integer to it, how does the system know it's an error versus the programmer intentionally wanted implicit conversions done? In that sense I'd put Java above Python for beginners, despite Python having the simpler syntax and rules.
It's perspective though. For me, I do lower level languages and experience shows that it is easier for someone who knows lower level languages to learn high level scripting languages than vice versa. Knowing the relationship of what the program does and how it affects the machine underneath is important. In scripting languages it's normal to be a bit loose and free with the rules, the goal is to get 'er done. For low level languages the goal is often correctness, reliability, and performance.
Best class I think I had at university of Comparison of Programming Languages. Good at a theoretical level, but also because homework involved using other languages with wildly different approaches. Ada, Lisp, Prolog, etc. Such stuff gets you out of the mindset that programming is just doing sequential operations, and that there is more than one way to structure code and data.
This was for a device not the web, and I needed the binary data. It was only used as key/value holders, no such thing as URI or MIME exists on the system. There was no need for JSON but someone felt it was more "standard" than a different protocol we had been using. Thy syntax was the only specification I could find at the time, no description of how to specify something other than numbers or strings. On hindsight I probably could have just looked at some Javascript documentation.
It's not that Pascal is less complex that makes it good, another important fact is that it enforces good programming. We taught it to freshmen decades ago and those who already knew some BASIC wo proclaimed loudly that they were already good programmers would bitch and whine about how hard all the structured code was and why did they had to declare variables before using them.
A doctor of philosophy gets a pondering instead of a calling.
But they're going to need the people with a career/profession/calling somewhere in the mix. Sure, the coders on the digital assembly line don't need to be the best, but you do need someone out there who's got more experience and education to design the system. Except with apps of course, apps are generally standalone pieces of fluff for the most part, no one cares about maintainability, performance, or reliability, so you can get an intern for that or else outsource it.
I disagree a bit here. The biggest failing I see in computer science is in trying to teach the popular languages like it was a mere two year trade school. Good programmers can learn any language, they don't need the university to teach it. Of course, the most popular languages may become the ones that are taught in higher level courses, that's just natural. But when a curriculum is derived around teaching what's popular then it loses a lot of academic value. A beginner's language while learning however may not necessarily be the most popular language. I started in Pascal, and it was great for teaching compared the other other popular languages because it enforced structured programming and strong typing from day one.
In my 30+ years of programming, the worst programmers who caused the most damage were the ones who thought they were hot shit superstar programmers, despite making the same boneheaded errors all the time. Generally they wanted to work solo and never as a team.
They usually got filtered out as freshmen when I was in college, in the intro to programming class. That class was never going to teach you enough to get a decent job in programming, and was not intended to do so anyways. A few students felt compelled to be in the courses though, because their parents had picked out the career for them.
Yes, I found that when I needed to do JSON parsing that it was vaguely defined. You need to know other stuff before you can proceed, which is why I really hesitate to call it a standard because so much is missing in the very short specification I read. The specification does say reasonably clearly how to parse, but not how to interpret the data that gets parsed. The stuff you need to know is that this is Javascript code compatible, thus the data types are the same as they are in Javascript, and strings can be used to encode binary data using base64, etc. Also imagine that there is an implicit "{" and "}" surrounding all of it.
JSON is a lot smaller. No schemas, properties, etc. It's just data definition and nothing more. Store your data in a bulky format, read it back again, send it over the network in a bulky but device independent manner, etc.
The reason for its existence is precisely because it is Javascript subset. No one invented a new library for it originally, it was just snippets of Javascript data declarations that someone used on their website.
Not for XML, but for JSON, I wrote my own library. Had to, one did not exist for the device that met the requirements. Not everything is a PC. And if you do want proper libraries, they will still disagree with each other! One problem I have seen more than once is the assumption that a library is correct merely because it's a library from a third party (as in my fellow coworkers are morons but anyone outside the building clearly has a comprehensive understanding of all the standards and was given enough time to complete the feature without ever feeling rushed).
JSON as a standard is very weak. It's hard to find a well defined specification suitable for implementing. There are a lot of assumptions made. Ie, how do you store binary data? Normally base64 but nothing requires this or specifies what base64 is and how it must be represented and what to do with the leftover odd bytes at the end. But everyone sort of knows as vague tribal knowledge what to do (do what Javascript does, do it the same way Python library does it, etc). It's a simple format, it has much going for it, but it's not formally specified.
For a while, all the cool people stopped wearing them, looking at you like a hopelessy out of touch dinosaur if you kept a watch. Then very quickly that reversed itself, now all the cool people and hipsters wear smart watches, Fitbits that tell time, and other time telling devices worn on the wrist. AND normal old fashioned analog watches are appearing on peopel's wrists.
The lack of wrist watches was one of the shortest lived fashion trends that I can remember.
In the US this is not exactly true, the government is not above the law. The executive does not make the laws, it only enforces them. Even though congress makes the laws it changes its mind very often. The courts can also step in and declare the a law conflicts with other laws. Presidents often discover that things aren't so easy to implement as they think they are before coming to office.
And yet winning lawsuits against the government has happened in the past. The US government is not unified, the courts, legislature, and executive do not agree with each other. We have had overreaching intelligence activities slapped down before by congress and the courts.
I only got texting recently, and my mother doesn't have texting and would never be able to figure it out.
Political parties are all about, at their heart, marketing. The only difference from your average telemarketer is the lack of quality of the product they are selling.
Not true. I get voicemail from family all the time. Since it's on the phone they assume I will see it eventually. The phone calls don't get through because I won't answer the phone all the time, I may be in meetings, drivings, at the store, etc. That's the whole purpose of voice mail so that the phone stops becoming your master and demanding that you respond NOW or else!
Deportations under Obama administration were higher than under any other president, it's really a stretch for some people to call him soft on illegal immigration given the numbers.
Nothing above the law about sanctuary cities. The federal government can request assistance with immigration enforcement but the local governments are not compelled to cooperate. There is no law that says they must assist the INS on demand.
INS claims (falsely) that they're only focusing on undocumented immigrants if they have committed serious crimes, and in such cases even sanctuary cities cooperate and turn the prisoners over. The case that riled so many against sanctuary cities when an illegal immigrant killed someone in San Francisco, there was no active warrant for the killer and there was no reason to continue detaining him. ICE requested he be detained but there was no legal basis for further detaining. The killer had no history of violent crimes, his deporations were due to drug laws and attempting re-entry to the US.
Now would it have been above the law to detain a person when no charges had been filed, no warrant or evidence presented, but merely because a federal agent asked for this?
It's not a filler-filled pile, it's just full of fiber*.
(*) warning, may contain nuts.
Ural nuts.
Right, but you still don't count that revenue twice.
Doesn't matter, Trump doesn't write the proposed budget personally. Hopefully he at least reviews the budget, but he's certainly not sitting there with a calculator and green eyeshades.