coreyoconnor
The flip-phone style ones: Excellent! The folding aspect really aids in switching between a small device with minimal controls to a normal phone. I would use these over a standard phone. No question.
The portrait-to-not style ones like pixel fold? Is nice on occasion but the software is a complete let down. For reasons I do not care: The orientation is either wrong or the software cannot handle the form factor. The end result is a poor user experience.
Considering "usable space" as a percentage of the screen that contains useful content these are worse when unfolded than folded. Yes the screen is larger but most of the screen ends up useless. The actual useful chunk suddenly becomes horribly small in proportion.
The default layout showing composing an email in gmail is a prime example. The actual content area of the email: Same size as when folded. The rest of the screen is unused or taken up by the keyboard. Yes the keyboard is now larger but it's somehow weirdly proportioned.
There are adjustments that can be made to improve that. Some have to be applied every time the phone is unfolded or the apps restart (or neither or both who knows?)
Oh and my pixel fold screen has failed 2x in 3 years - I do not treat it gently.
I go on a longer rant about this here https://youtu.be/WHxOosmJt_U
I do use AI extensively and get it to spit out vaguely acceptable designs. But I'm doing the design. Even when i have another agent trying to simplify or such the design details are still me.
I don't think people understand how this runs in contrast to the claims of intelligence.
I suspect if such a filter was applied there would be very few. Probably just the bindings to gtk, qt or appkit.
This is not how I'd design much of this. Does that matter? AI and whatever training data used seems to differ.
1. google pixels are the best android devices AFAICT. Not a high bar, but that's that.
2. due to the prevalence of spam and scam calls: Not having an AI call filtering is a no-go. google pixel's have a really nice call screen.
Course we could have a competent government that would do something about scams (besides encouraging and supporting them). Then small business could actually compete. But the best we get is a rapist and scam artist.
I did not know about the jira shortcuts until recently. Not really a huge deal for me. Seems like linear's are definitely better but shrug. Keyboard shortcuts are not the source of my issues (ha!) with issue trackers.
Confluence shortcuts tho. I'm pretty sure I'm the only one in my company that knows them haha. Which says something about confluence for sure.
At glngn we didn't use akka streams (outside of akka http) but did use event sourced, persistent entities powered by akka typed in clustered mode. Deployed to k8s. Which definitely took effort to set up nicely and enable smooth deployments. Our clusters were not huge so many problems did not show up (split brain).
I haven't used other systems that provided an equivalent to akka typed persistent entities. I can't compare akka in that sense. However the event sourced persistent entities model is really, really effective. Definitely a different paradigm: some stuff is trivial that would otherwise be a trial.
I suspect many of the benefits could be achieved by using something like Kafka feeding non clustered nodes. But never tried.
Interesting juxtaposition haha.
There are likely multiple root causes. The whole space of issue management around libraries and applications using those libraries is a horrible and abusive mess. In my experience, between an application using a library and a library users will target whichever is easiest; not most applicable. Plus, most opensource user support is a fucking chore (you'd need to pay me for these days) that's unsustainable.
Another cause is likely the cost of nixpkgs contributions themselves. Personally, I no longer contribute to nixpkgs because even for tiny changes the process is ridiculously expensive. That's not including the cost of getting up to speed with nix/nixpkgs and the, often, highly opinionated packaging.
nixpkgs needs to be broken up into multiple independently distributable packages.
How? Is it some complex chunk of code that requires a delicate hack?
No, not at all. There is literally a function with code, more or less, like: "If owner then OK here's all the funds". Anybody can check this in the contract. Yet people are dumping funds into these contracts. Even tho these contracts tend to only attract a few thousand dollars each. Well, costs next to nothing to create and spam.
A more detailed analysis of a similar contract to the one I've seen: https://cryptot3ddybear.gitlab.io/blog/posts/scam-explained-...
As for licensing: totally agreed. I would like to see more projects with protective licensing.
Too many projects are basically donations to Amazon.
What does AWS gain by improving IAM? There are barely any competitors, so they won't be losing people for that. They offer their own AWS professional services happy to charge you for making it "understandable". Their service agreements largely absolve them of client mistakes. Which usually result in larger bills from AWS.
Scala has a history of embedded domain specific languages that are difficult to understand. (Rather like Perl now that I think about it.) This is not universal in scala EDSLs but definitely exists. So it's a fair concern in general. IMO Chisel is a nice EDSL so, in this context, the concern is unwarranted.
Seriously tho. When I was employed by them their agreements were by far most draconian compared to any other company I've worked for. Ridiculous.
Most companies I've worked did have a route to enable you to contribute to projects outside of work and still retain the rights. Tho the easiest route is to establish something within a domain you want to work and then state that on a "inventions and copyrights" pre-employment agreement. This will outright eliminate you from certain jobs but... That's the US for ya.
Location: Seattle, WA
Remote: Yes
On-Site: Yes, no relocation
Technologies: Scala, Ruby on Rails, Ansible, Jenkins, Nix, NixOS, DynamoDB, Postgres
LinkedIn: https://www.linkedin.com/in/corey-o-connor-389ab23/
GitHub: https://gitlab.com/coreyoconnor/
I know these won't actually succeed in adding a bit of capitalism but it does succeed in highlighting the absurdity.