Why, for the love of the gods, is there a separate Microsoft Teams for "work or school", I mean this is just sloppy software design. Also, lol at "Microsoft Teams is generally available" on the download site. I mean I'd like it to be always available but if that's the best you've got...
@CatherineFlick Teams also does not allow the user to login to multiple accounts on their Mac/Windows' versions. Their iPad/iPhone versions allow this. No wonder Teams is not picking steam in spite of Microsoft giving it away for free
@hazelweakly Kubernaughties currently exists and has been promulgated just as a shrine to the egos of people who work(ed) at Google. That it has become so prevalent despite its complexity is because all the startup bros who want to add "snake-oil fairy glitter" to their resume.
Figured out today that the latest oracle jdbc driver is broken generates spurious failures. 100% reproducible so that's good at least 😀
Fun day tomorrow figuring out which version is safe to use
Upon first encountering SQL I thought I had stumbled into hell. I quickly realized that was optimistic: after all, hell has rules.
I have since realized that SQL does too, and that they are no more confusing than those of other programming languages. To quote Pratchett, it is not mad, just differently sane.
Welcome, then, to a world in which the strange will become familiar, and the familiar, strange. Welcome, thrice welcome, to SQL.
@gvwilson This tutorial you put together is exhaustive, and amazing. I will be asking my 10th son grade son to use this for learning SQL.
But, pray tell me where is "hell" in SQL, and why. SQL is not without its issues, but there is a reason why SQL is ubiquitous, prevalent, and successful. It works as promised, and for most part decipherable. If as you claim, SQL is hell I'd like to introduce you to Haskell, Scala, and Node.
@hazelweakly@gvwilson SQL in the ANSI standard form is great for about 90% of the usecases/cases. The 10% should be attributed to how databases optimize. The same Query written in SQL-Standard works accurately across databases providing the same results. Where they differ is in performance. And that is where the "hell" you are referring here come in to play. That "hell" has more to do with underlying databases and not with SQL itself as a language.
Spent the whole day debugging a #React error for my son's STEM school project. No solution, and google hasn't been much help. FWIW, the code was written by 10'th graders and not that organized. Still better than a lot of #bootcamp grads.
I told him to create a new project from scratch and do it properly. Wish me luck when I pair-program with him tomorrow
Prediction: at least 90% of orgs doing "cloud repatriation" (aka "how hard can it be to run some infrastructure, ffs?") are going to get a nasty shock when they re-discover all the reasons that people moved to cloud in the first place: running infrastructure at even modest scale is absolutely not trivial.
Combine that with re-discovering all the basics of hand-offs, on-call, and other DevOps 101 stuff, it's going to a wild fscking ride 🏇
@matthewskelton Come on!!! All these shrines built to the ego of #DHH will go to waste. Everyone will bow down to DHH and ask him to come save them. He will then descend on a RoR chariot and berate them for using the cloud in the first place. Then all the cultish followers will lash themselves with cat-o-tails at the end of the Turbo framework
@danjac I am probably in the minority, but in my experience Flutter is far superior compared to React Native for cross platform development. Performance of the Flutter Native apps have been far better than React Native.
@alxlg@fallenhitokiri@kiwa@elisse
Element is a usability, and accesibility nightmare for even tech-savvy people. Just this year alone I've been part of 6 different migrations where startups have moved from Slack to Element for its security features. Every single one moved to either Microsoft Teams or Mattermost within a month. 2 of them had a revolt and the engineers reverted to email for realtime collaboration. #Element has lost the #usability battle when Microsoft seems a better option.
You are using a data point of 1 versus data points from 6 different companies. This extrapolation is being disingenuous at best
Like it or not, Element is the face of Matrix; they are inextricably linked. By this measure we might as well say "Lynx is usable, what's the hoopla of Safari, Chrome, or Firefox".
1/
@alxlg@fallenhitokiri@kiwa@elisse
3. The success of Matrix is very closely tied to that of Element. With its current approach, Element does not seem inclined to gain traction with enterprise customers
4. If I am a tech-focused company, I would be very wary of using Matrix/Element to be the face of support for usability reasons (not just Element, but the protocol itself). A lot of my peers in the tech leadership space feel the same and are holding off on the exodus to Matrix.
2/
@webology
IMHO, Satya turned this coup into a victory for himself. Genius
He got the 2 cofounders to lead Microsoft's AI. While the cofounders are assholes and unethical, they fit right in with Microsoft's ethics (or lack thereof) and boosts Microsoft's AI credibility
He neutered Sam's ambitions to compete against Microsoft's AI chip.
Inmates running the #OpenAI prison 505 of 700 (Illya #12 on the list) employees telling board to resign. No matter what, #OpenAI is well and truly screwed
"Modern apps expect too much to write everything from scratch"
I was able to write highly interactive apps with vanilla JS, Alpine and HTMX, a couple dependencies.
I really, really don't get the "frameworks are good for DX" argument. Every production React codebase I have worked on has been a horrible shitshow, about the worst DX you could imagine.
@danjac Frameworks are meant to support DRY. Instead they end up being ARID - Agonizingly Repeating Inane Drumbeats . The original idea of framework(s) is to make DX better. But front-end frameworks have raced past backend frameworks like Spring, RoR in terms of complexity and unusability.
Thankfully that is chanigng with the emerging popularity of HTMX, VanillaJS, Turbo, etc
@danjac@starbreaker#Tesla is a tin car killing machine. The car sees a plastic bag flying towards you, and the AI goes #Skynet on you. It sees the bag as the moon falling out of the sky and drives you into a ditch, the center divider, or into the ocean with the express intent of killing you. It has no "kill switch" (pun intended), and no manual override to stop the car if the shitty AI in the machine fails.
@danjac React is still fine by me because the skills can be "ported over" to VueJS. Node.js on the backend is a big no-no. These engineers have no demonstrable sense of building scaleable applications. For them resources like memory and CPU are dime-a-dozen.