Yeah, yeah, of course. But c'mon. To mention "credit cards" and not complete auto financing seems surprising, to me, given the entities that are involved.
It says the leak doesn't include any credit card information. Uh...who buys a car with a credit card? What about loan/bank/financing information? (Not to mention SSN, DOB, address, et cetera.)
A difference in your return doesn't indicate anything about whether you paid more or less tax compared to earlier years. You may have paid less tax and also seen a lower return because your withholding changed.
My return dropped this year, so I'm part of that trend. But I also paid less tax this year.
At one time, Java was my most-used language, dominating the server-side and also being used for Android. These days, my most used languages are ECMAScript/JavaScript on the server (and browser), Swift for iOS, and Kotlin for Android.
I don't think my anecdotal experience is evidence that Java is dead or dying, but it wouldn't surprise me if Java's use is declining, generally. But that's no big deal. Originally, my most used language was C. Then it was C++. Then it was Java. Et cetera. But C isn't dead. C++ isn't dead. Java's usage may decline, but I doubt it will "die" for a long, long, time.
Also, there's the JVM aspect to consider. Languages other than Java target the JVM: Kotlin, Groovy, Scala, Clojure, et cetera. I wouldn't be excited about coding in Java, these days, but I'm happy to code in Kotlin or Clojure.
According to comments on the AUR acroread package, the script the compromised package installed (to upload system details) contained an error and wouldn't function properly. The script also installed a systemd timer, and the comments advise checking your system for:
/usr/lib/xeactor
/usr/lib/systemd/system/xeactor.timer
/usr/lib/systemd/system/xeactor.service
As a side-comment, for those unfamiliar with Arch, these compromised packages are not part of the official Arch repositories. The AUR is a "user repository": a collection of user-supplied packages which require deliberate download and installation. AUR packages should [i]always[/i] be reviewed before installing them, and not installed if you don't trust the package. As the AUR documentation explains, "Warning: Carefully check all files. Carefully check the PKGBUILD and any.install file for malicious commands. PKGBUILDs are bash scripts containing functions to be executed by makepkg: these functions can contain any valid commands or Bash syntax, so it is totally possible for a PKGBUILD to contain dangerous commands through malice or ignorance on the part of the author. Since makepkg uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list."
C++ and JavaScript share a common issue, in that both languages have some design problems that they carry with them, but both are popular and have layers of syntax accumulation and libraries, and both will allow you to write some terrible code.
However, if you have a firm understanding of the languages (and the pitfalls particular to each), you can also write solid and elegant code in either language. It's more a matter of avoiding their bad parts than anything else, but it requires knowledge and discipline to confine yourself to the "good" subset within each language.
No doubt we'll pay for the "new jobs" this creates by taking some money from everyone else's paychecks. Or we could just create some new dollars and spend them before the market adjusts prices to account for the increase in the amount of currency. Kind of a "stealth tax" on your savings account (we don't directly take your dollars, but they buy less than they used to). The possibilities are endless!
Linux is my main OS, but I see no compelling reason to run Linux as the native OS on a MacBook. If you want to run Linux on a laptop, get a laptop with better specs and run Linux on it. If you want a MacBook, just run MacOS.
The primary reason I own a Mac is for Xcode and iOS development. I'm hoping Apple updates the Mac Mini soon. If they do that, I'll get a Mac Mini for iOS development and replace my (aging) MacBook Pro with a Linux laptop. (I run Arch on my desktop/workstation, but I might give Ubuntu a try on a new laptop.)
I didn't take JS seriously until after I read Crockford's book. That was illuminating. Even older versions of JS can be okay if you understand the nature of the language and what you should avoid. And I agree it's (mostly) gotten better. Using modern ECMAScript is actually pretty nice.
I was on a team that "used agile" for while. The thing is, our development workflow "before agile" already addressed the main ideas in the agile manifesto, so in practice what happened is that our development workflow was unnecessarily modified (disrupted?) to include more "agile practices" like pair programming and other buzz words (user stories, rigid application of TDD, et cetera). We didn't see much (any?) real benefit. It eventually got abandoned. Can't say I miss it.
I've got no problems with the ideas in the agile manifesto. I'm just not convinced that the practices and culture that often gets included are always worthwhile.
Most used languages: Swift (for iOS) Kotlin (for Android) C# or VB.NET (for server-side - the company I work for has a MS server stack) JavaScript (for web)
Over the history of my career, the most used language is probably Java (for server-side, for Android, and even for some client applications), followed by C++ and C (for desktop applications and embedded systems). For iOS, I used Objective C until Swift came out.
As far as preferences, I like both Swift and Kotlin (and prefer them over Objective C and Java). JavaScript has grown on me, despite its warts. I find it nice if you use some of the modern features (Babel helps) and avoid its pitfalls (the "bad parts" -- a good linter helps with this). That said, JavaScript is a language that makes it easy to screw things up if you don't understand it well, so I get the hate that JavaScript attracts.
I put Java and C# in the same category, preference-wise. I can code in them just fine, but they're not my favorites.
I also put C++ and C in the same general category. If I'm using one of these, I'm probably doing something where I'd have a mild preference for C.
VB.NET is not something I like to use, but something that I have to use. It's at the bottom of my preference list. I don't like the syntax and find it verbose, ugly, and inelegant.
I drink coffee and water when I'm coding. I listen to whatever I feel like. Usually rock or classical, but sometimes jazz. I sometimes code on the weekends (hobby stuff, not work). I probably average 7-8 hours of sleep a night. I use Xcode for iOS, Android Studio for Android, Visual Studio for.NET stuff, and editor + bash shell for JavaScript. I prefer a dark theme for my IDE or editor. For editors, I'm fine with vim, but lately I've been using Atom. I also recently tried Visual Studio Code, which is surprisingly good. My company's server's are mainly self-hosted, but we also have some AWS and Google cloud stuff.
That's possible (although I'd also say it's possible for non-rolling releases), but it hasn't been my experience with Arch. YMMV, of course. Some of it may be hardware and driver dependent.
I'm a professional developer. I prefer Arch (and don't have any problem keeping it up to date and stable). I think you're mistaken about it being "trash." That said, if you prefer something else, I don't mind.
I've run both rolling and non-rolling distros over the years. All I can tell you is that, yes, I prefer a rolling release distro for my workstation. I've been running the same install of Arch for several years, now, and there have only been a couple times that applying updates caused me any issues. I run updates once or twice a week, and before running them I check the Arch news for any gotchas or pre-update tweaks I might need to perform (uncommon).
Personally, I wouldn't run Arch on a production server, but for a workstation or a home system I think it's great.
I know what you're saying (I run CentOS servers, too), but for my workstation (yes, for professional use) and for personal (non-work) computers, I much prefer rolling release.
Criticisms about these being pointless or impractical miss the point, in my opinion. These aren't for the general user wanting to browse the web and check Facebook, they're for hackers. They're for the same kind of geek that has an oscilloscope and a signal generator and a Raspberry Pi and breadboards: someone who likes to explore tech for its own sake. Somebody who wants to write new code for that custom Xena chip. Somebody who wants to explore off the beaten track.
Seems cool, to me.
I think OS/2 was a nice OS, for the time. However, it's time is past, and I can't imagine why I would want to switch to it, today (I run Arch on my main system and I have a Mac laptop for iOS development).
Slashdot Mirror
Yeah, yeah, of course. But c'mon. To mention "credit cards" and not complete auto financing seems surprising, to me, given the entities that are involved.
It says the leak doesn't include any credit card information. Uh...who buys a car with a credit card? What about loan/bank/financing information? (Not to mention SSN, DOB, address, et cetera.)
A difference in your return doesn't indicate anything about whether you paid more or less tax compared to earlier years. You may have paid less tax and also seen a lower return because your withholding changed.
My return dropped this year, so I'm part of that trend. But I also paid less tax this year.
At one time, Java was my most-used language, dominating the server-side and also being used for Android. These days, my most used languages are ECMAScript/JavaScript on the server (and browser), Swift for iOS, and Kotlin for Android.
I don't think my anecdotal experience is evidence that Java is dead or dying, but it wouldn't surprise me if Java's use is declining, generally. But that's no big deal. Originally, my most used language was C. Then it was C++. Then it was Java. Et cetera. But C isn't dead. C++ isn't dead. Java's usage may decline, but I doubt it will "die" for a long, long, time.
Also, there's the JVM aspect to consider. Languages other than Java target the JVM: Kotlin, Groovy, Scala, Clojure, et cetera. I wouldn't be excited about coding in Java, these days, but I'm happy to code in Kotlin or Clojure.
Mod parent up.
This isn't a "Linux 4.20" problem, this is Intel's fault.
According to posts on aur-general, the known affected packages are:
According to comments on the AUR acroread package, the script the compromised package installed (to upload system details) contained an error and wouldn't function properly. The script also installed a systemd timer, and the comments advise checking your system for:
As a side-comment, for those unfamiliar with Arch, these compromised packages are not part of the official Arch repositories. The AUR is a "user repository": a collection of user-supplied packages which require deliberate download and installation. AUR packages should [i]always[/i] be reviewed before installing them, and not installed if you don't trust the package. As the AUR documentation explains, "Warning: Carefully check all files. Carefully check the PKGBUILD and any .install file for malicious commands. PKGBUILDs are bash scripts containing functions to be executed by makepkg: these functions can contain any valid commands or Bash syntax, so it is totally possible for a PKGBUILD to contain dangerous commands through malice or ignorance on the part of the author. Since makepkg uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list."
C++ and JavaScript share a common issue, in that both languages have some design problems that they carry with them, but both are popular and have layers of syntax accumulation and libraries, and both will allow you to write some terrible code.
However, if you have a firm understanding of the languages (and the pitfalls particular to each), you can also write solid and elegant code in either language. It's more a matter of avoiding their bad parts than anything else, but it requires knowledge and discipline to confine yourself to the "good" subset within each language.
No doubt we'll pay for the "new jobs" this creates by taking some money from everyone else's paychecks. Or we could just create some new dollars and spend them before the market adjusts prices to account for the increase in the amount of currency. Kind of a "stealth tax" on your savings account (we don't directly take your dollars, but they buy less than they used to). The possibilities are endless!
Missing option: hot grits.
Linux is my main OS, but I see no compelling reason to run Linux as the native OS on a MacBook. If you want to run Linux on a laptop, get a laptop with better specs and run Linux on it. If you want a MacBook, just run MacOS.
The primary reason I own a Mac is for Xcode and iOS development. I'm hoping Apple updates the Mac Mini soon. If they do that, I'll get a Mac Mini for iOS development and replace my (aging) MacBook Pro with a Linux laptop. (I run Arch on my desktop/workstation, but I might give Ubuntu a try on a new laptop.)
I didn't take JS seriously until after I read Crockford's book. That was illuminating. Even older versions of JS can be okay if you understand the nature of the language and what you should avoid. And I agree it's (mostly) gotten better. Using modern ECMAScript is actually pretty nice.
I was on a team that "used agile" for while. The thing is, our development workflow "before agile" already addressed the main ideas in the agile manifesto, so in practice what happened is that our development workflow was unnecessarily modified (disrupted?) to include more "agile practices" like pair programming and other buzz words (user stories, rigid application of TDD, et cetera). We didn't see much (any?) real benefit. It eventually got abandoned. Can't say I miss it.
I've got no problems with the ideas in the agile manifesto. I'm just not convinced that the practices and culture that often gets included are always worthwhile.
Most used languages:
Swift (for iOS)
Kotlin (for Android)
C# or VB.NET (for server-side - the company I work for has a MS server stack)
JavaScript (for web)
Over the history of my career, the most used language is probably Java (for server-side, for Android, and even for some client applications), followed by C++ and C (for desktop applications and embedded systems). For iOS, I used Objective C until Swift came out.
As far as preferences, I like both Swift and Kotlin (and prefer them over Objective C and Java). JavaScript has grown on me, despite its warts. I find it nice if you use some of the modern features (Babel helps) and avoid its pitfalls (the "bad parts" -- a good linter helps with this). That said, JavaScript is a language that makes it easy to screw things up if you don't understand it well, so I get the hate that JavaScript attracts.
I put Java and C# in the same category, preference-wise. I can code in them just fine, but they're not my favorites.
I also put C++ and C in the same general category. If I'm using one of these, I'm probably doing something where I'd have a mild preference for C.
VB.NET is not something I like to use, but something that I have to use. It's at the bottom of my preference list. I don't like the syntax and find it verbose, ugly, and inelegant.
I drink coffee and water when I'm coding. I listen to whatever I feel like. Usually rock or classical, but sometimes jazz. I sometimes code on the weekends (hobby stuff, not work). I probably average 7-8 hours of sleep a night. I use Xcode for iOS, Android Studio for Android, Visual Studio for .NET stuff, and editor + bash shell for JavaScript. I prefer a dark theme for my IDE or editor. For editors, I'm fine with vim, but lately I've been using Atom. I also recently tried Visual Studio Code, which is surprisingly good. My company's server's are mainly self-hosted, but we also have some AWS and Google cloud stuff.
Are you entertained?
Lately I've been using Kotlin for Android development. It's nice (way better than using Java).
Those numbers put together like that are inane, and smack of a sensationalist, agenda-driven goal, not meaningful science.
That's possible (although I'd also say it's possible for non-rolling releases), but it hasn't been my experience with Arch. YMMV, of course. Some of it may be hardware and driver dependent.
I'm a professional developer. I prefer Arch (and don't have any problem keeping it up to date and stable). I think you're mistaken about it being "trash." That said, if you prefer something else, I don't mind.
I've run both rolling and non-rolling distros over the years. All I can tell you is that, yes, I prefer a rolling release distro for my workstation. I've been running the same install of Arch for several years, now, and there have only been a couple times that applying updates caused me any issues. I run updates once or twice a week, and before running them I check the Arch news for any gotchas or pre-update tweaks I might need to perform (uncommon). Personally, I wouldn't run Arch on a production server, but for a workstation or a home system I think it's great.
I know what you're saying (I run CentOS servers, too), but for my workstation (yes, for professional use) and for personal (non-work) computers, I much prefer rolling release.
This kind of thing is one reason I switched to a rolling release distro (Arch, in my case). I won't be going back.
Whatever Happened to Penny Candy? (Richard Mayberry) Economics in One Lesson (Henry Hazlitt) The Law (Frederic Bastiat)
This. Wish I would've read this around 14 or 15.
I may recommend that the useless blueshirts get stuffed.
Criticisms about these being pointless or impractical miss the point, in my opinion. These aren't for the general user wanting to browse the web and check Facebook, they're for hackers. They're for the same kind of geek that has an oscilloscope and a signal generator and a Raspberry Pi and breadboards: someone who likes to explore tech for its own sake. Somebody who wants to write new code for that custom Xena chip. Somebody who wants to explore off the beaten track. Seems cool, to me.
I think OS/2 was a nice OS, for the time. However, it's time is past, and I can't imagine why I would want to switch to it, today (I run Arch on my main system and I have a Mac laptop for iOS development).