This is slightly off topic. But PHP has a great devloper experience, in general, now with vscode, and autocomplate, find all references, etc. But the best framework out there is Laravel. It's great, but the maintainer doesn't seem reliable. Every single release has some type of backwards incompaitible change to it of which they don't document all the changes. So it's basically a blackbox if you are to upgrade your laravel/framework version.
I've heard this criticism of Laravel a couple times and never understood it. I've been using the framework for years and have never had an issue with upgrades. There is a clear and comprehensive upgrade guide with each release, as well as a third-party package called Laravel Shift that can inspect your code and perform automatic upgrades in many cases. I've found there are only one or two breaking changes per minor version release (which seems reasonable to me), and they are always well-documented.
Aside from that, I'm glad you've highlighted Laravel, which—despite being the most popular server-side Web framework on GitHub—gets virtually no attention from HN. It's typical to use Laravel in the old server-side rendered Rails paradigm (which is still probably best for some applications), but I've had success using it to develop APIs as well. Core features like the ORM, job queues, dependency injection, email templating, etc, are very solid, and the ecosystem of packages around it is phenomenal. I would recommend it to any Web developer.
Laravel also as a lightweight version called Lumen for simpler APIs and things. It includes a lot of the features of core Laravel but has a more stripped-down application structure.
Ok. I agree vert.x and quarkus.io really look promising! I was using the play framework which looked similar at first glance and then was horrible as java was just at the surface and one needed to use scala in the end. Learning scala with a java team under time preasure was not a good experience...
I did Play v2 with Scala... I can agree, it was not pleasant. (I had just gotten off a year-long Ruby on Rails/ JRuby on JVM stint though - so "pleasant" is a relative term)
How come it has a best developer experience? Even setting up xdebug and starting debugging is a pain. Most of the developers codes in php use `echo` for a long time.
PS: I haven't used php for 2 years, let me know if there is an update on debugging.
Yes I totally agree that setting up or rather understanding how the debugging cylcle works with php is not straight forward. It doesn't work out of the box and one has to dig into php internas. However, it pays off, as one can do remote debugging on e.g. a docker development machine or similar...
I am not sure how well such a feature is supported in javascript, ruby, java or what not out of the box...
And most of the rich people in my neighborhood have complete voice devices in their homes, Amazon’s device and Google’s I refuse to have these devices in my home regardless of how cool they seem.
Some people have no problem putting a little webcam in their toilet bowl so that the world can watch them eliminate every morning. Personally I prefer to keep my business private. I don't need any "vindication" to be happy with my decision to protect my privacy. If you don't understand the value of privacy nobody can explain it to you - but they may watch your morning broadcasts.
You don't see any difference between people getting a Google-connected device (like a Google Home or Pixel phone) and those that install a public webcam in their bathroom?
Political turmoil. Putting this data in the hands of FAANG means it's just one NSL away from being used by the government.
It's foolish to think that the relative stability of western governments since the 1950s is a permanent condition. This is a blink of an eye in historical terms.
At it's core, this is just "whataboutism". Yes, phones have a lot more sensors. Phones also give you some control around what gets recorded when. Even if phones were just as bad, doesn't mean the solution is capitulating completely and putting listening devices all over my house. Quite the opposite actually.
As an aside, this is why I would never use an Android phone. At least Apple, for all their faults, allows me to keep my data on my phone and treats privacy, user consent, and app permissions as serious matters. Meanwhile, Onavo is still available in the Play Store[1].
Edit: It's telling that you didn't respond to my reasons for why this technology is potentially harmful, and instead just reached for "but what about phones?" I would love to hear your argument for why corporate or government abuse of data from always-online, always-listening devices like Alexa and Google Home is not a real concern.
I reached for "what about phones" because these devices seem very similar except they have a better speaker and fewer sensors. The Google one even runs Android IIRC. If I say "OK Google, who does Hunter Pence play for?" and my Google Home answers the query rather than my phone, what's the difference?
Frankly, they seem like less of a privacy concern to me than a smartphone because they don't also track my movements.
> I would love to hear your argument for why corporate or government abuse of data from always-online, always-listening devices like Alexa and Google Home is not a real concern.
It is a concern, just not a big one. I use an Android phone (and an iPad) so I figure that horse have left the barn. I'm willing to accept some risk if there are benefits. For example, I risk my life every time I drive my car. If I'm willing to take on that very real risk, why would a hypothetical about an internet connected device doing much less harm scare me?
Your point about using Apple exclusively is a good one. If I were more worried about it I would do the same.
I believe there's either a trigger somewhere in Amazon's or Google's PR to post the classic 'but what about ur phone' whenever someone is pushing back against IOT recording devices or we've become so brainwashed that we do their job without even realizing it. I don't know which of the two is sadder.
What's the difference between a Google Home and a Pixel phone sitting side-by-side on the table, which one is the bigger threat to my privacy? What about when I leave the home and take my GPS-capable phone and leave the Google Home on that table? Which is a bigger threat now?
No, you've got him all wrong. Zuck is sorry about all of this. He's said so since 2003, also in 2006, and in 2007, and in 2008 (four times), also in 2010... it goes on to this day. He's incredibly and perpetually sorry for being a total scumbag: https://www.wired.com/story/why-zuckerberg-15-year-apology-t...
Related note: when my 3-year-old says he's sorry, but keeps punching his sister, we put him in time out.
> Maybe it's just because white collar people are forced to sit at a desk all day,which is unhealthy and takes a very obvious toll on the appearance of your body
You're joking right? Have you ever talked to or a seen a real labor worker?
Yes, exactly. Working a desk job is cushy in many ways, but long term sitting is terrible for you and it will be reflected in your muscle tone, posture, etc.
What you're describing is a legacy, traditional, (and terrible!) 'ops will fix it' mentality that often permeates larger companies where dev teams 'throw stuff over the wall' to another team for production deployments, outage triage, etc
A company with a devops culture deeply involves both developers and operations oriented folks from the start of a project to ensure best practices, reliability, and observability are being baked in from the start, that deployments are automated, and usually developers are more directly responsible for and involved in the operations of their software rather than having dedicated 'ops' teams doing 'firefighting'
Read some of the content put out by Gene Kim or Martin Fowler for a much more in depth look at devops culture and the benefits it can bring a company.
Prioritization problems exist independently from release cycle problems. "Everything becomes an emergency" is a symptom of broken priorities, not fast releases.
If you're in the habit of doing 24 hour turnarounds, then a 24 hour turnaround is no longer an "emergency", it's just normal process. No reason to panic, or to act panicked. Emergencies are only emergencies if they interrupt work-in-progress.
The problem is not releasing 24 hours after you start working on something. That you can plan for.
The problem is when you discover something to work on and want it released in 24 hours then you are throwing away any existing schedule as you can’t plan for what you don’t know about.
Call it an emergency or just day to day operations, but the only way to work like that is to give up on the idea of a schedule of any kind.
So then I have confirmed it. I read about browsing the internet and generally no one working 8 hours a day it they work in software. Some days I literally don’t have work to do, so I browse the internet. Sometimes it’s nice to work on tasks around the home if I am working from home that day.
Management must know this. I consider it an unwritten/not talked about fact of working as a software developer.
Why would you bother staying at work if you have nothing to do. Take your laptop home and VPN for OC issues if that’s why.
But I can’t unders how you can have nothing to do. If you feel like doing nothing, that I understand. Some days just don’t work. But having nothing to do is quite surprising.
Unfortunately we only branch on release. We don’t have separate branches. Consider it as everyone working on master, and no merges m, just code reviews.
>>Some days I literally don’t have work to do, so I browse he internet.
Go home, that's the nature of the job. You earn your money on a few big projects for the entire year, but you are needed for the next round.
Alternate and keep track so the team gets a break and are somewhat indebted to the company. Maybe a few stay on call just in case...depending on the job.
It should be pretty obvious to anyone that's used both JIRA and it's competitors that it's a piece of shit. It's missing basic functionality that competitors have like live updates (I guess I'll just telepathically guess when my teammates have made an update and hit F5), it's got basic UX problems that everyone else seems to have solved just fine (opening outbound links in a new tab etc), and their new redesign appears to have done fuck all to make any of it better.
I don't care how many features it's got for BAs/PMs to wank over. If the basic usability isn't there, the devs won't proactively participate, which means they'll either be forced to (incurring a big hit to morale), or they'll use other tools like Trello or physical boards to organise instead, and you end up with multiple sources of truth and synchronisation problems.
How it's ever become so popular is a mystery to me. I wouldn't inflict it on a team of my worst enemies.
Hmmm...I don't really share the same opinions about JIRA. Complex teams with a lot of stake holders and JIRA was light years better than what was used before. Maybe you just have super simple needs? I also don't see at all what's so complicated about using the tool, and my org has some super complicated customized workflows to get a ticket to flow efficiently through all facets of the org. Also, even on our smaller teams, that have simple processes right now, people can open up and create a ticket easily with most of the effort in filling out the description?
Even more concerning is that you state your devs would have negative morale by being forced to use this tool? You must have bigger issues?
Interesting. These seem like relatively minor issues to me. We switched from Asana to JIRA about a year ago. We spent about 2 years using Asana, and I hated working with it daily. JIRA is very far from perfect but like it many times more. We have significantly better understanding of where our team is and our projects now, and we scoured the web for every way to use Asana we possibly could find. To each their own...
One of the things that bothered me the most about Asana was how slow it was (also a UX issue).
