soulnothing

From an 11th gen I get about 6 to 7 with light usage, two to three with any development. It's largely a thin client at this point. Battery health is at 92%.

I tried upgrading to the ryzen and when it was good it was really good. I was able to keep a user mode libvirt vm running for dev work and mid brightness under 5W power draw. That used slirp networking, adding a bridge or default nat nic takes up about 2w to 3w of it's own power.

But like most windows laptops the suspend mucked things up. Not even power draw while asleep, but when awaking from sleep the power minimum was 10w with it more often at 20w with similar usage. I tried several wifi cards, nvme drives, port configurations etc. Also tried Fedora, Ubuntu and Nixos.

On Linux this carries over to the discussion of tlp vs power profile daemon, and soon tund. I saw much better performance and regularity with tlp, but that seems like it's not the path forward.

The steam deck shows that suspend can be fixed and done well with decent battery life under linux.

Updated parent comment with links. The back 2 are USB 4 while the front are usb 3.2 is one thing.

Last I read, the USB a cards don't fully enter suspend in the os. I have an 11th gen and I pop out my USB a to save battery when I don't need it. The hdmi also used to have that problem but that's since been fixed.

I recently did a deep dive on gc issues at work, and compared eden the default collector and z.

Our app was collecting pretty heavily, and an average collection time of about 50ms. With Z, and Linux huge pages it was collecting sub millisecond. This was at the cost of a bit more cpu, as z uses more threads for collection.

Using gatling for performance testing, we saw a small increase in requests per second. But the benefit was a smoother response time, with less spikes to high p9X measures.

Using flight recorder with this is a great way to get details of how the gc is performing.

Addendum: As noted below zgc uses more memory, I only found it viable on 16GB heaps or above. With it really improving performance around 32GB.

Is there a chance of a hinge offering 2 in 1 capabilities? I.E. full fold back to tablet mode?

I medically can't drive, and my other half doesn't want to drive. I see this as well, a number of my circle also want walkable/transit areas. In the states it's NYC, Philly, Boston, Chicago, San Fran, Seattle and a bit more. I feel like I need to leave just to get a sane metro area.

I'm in NYC now, but keep circling back to Philly. We're renting for ~3200 now a one bedroom 650sqft in NYC, both work from home. To get the ideal separation we want, not have our joint offices in the living room, we would need to go to between $5,500 and $6,500. While in Philly we could get a trinity, small town house three floors plus basement, about 900sqft, in downtown for ~2200.

I wouldn't buy in Philly, I just don't trust the city planning at this point. They're trying, but it's an uphill battle. The tax situation as a self-employed was much more complex in Philly. Safety is not something to just shy away. I lived in Old City, two years back, and there were still shootings near my apartment. It's a problem in a lot of cities as we gut social spending and relief programs. Philly did open a safe injection site, and is making head way.

I really like Philly, close to NYC Megabus was 15$ a seat, and about 3 hours. Amtrak is even quicker. Great music and food scene, Reading is great for food / produce.

The biggest issue I've found is the job market. Locally, a lot shifted out to office parks, requiring regional rail, and walking along multi-lane roads. If you're working remote, I got cost of living adjusted like crazy. The quotes I got were 80% pay cut over my NYC rate. While local jobs, were only a 10% cut. The local tech scene is a bit behind, more legacy.

Comcast has a great VC program as well for startups. The city also has tax programs to help get startups in the area.

The weakest link in this setup is your current internet. I've found while traveling, internet is generally pretty bad under, 10Mbs. Making this a rather difficult task. American view.

At home, my "laptop" is a dumb terminal that docks to my desk monitors. But computes to servers in the closet.

At my families who have (150:down/10:up)Mbs it was no different from being at home. I connected over wire guard. I even took my zoom/client calls in vms over rdp. Passing my webcam from my local laptop -> wire guard -> server. I also used parsed to stream gaming from home.

Conversely, I was at an Airbnb recently with (5/0.512)Mbs DSL. It was a real chore. For the internet black hole, I've opted to go for a SFFpc instead. That can fit into checked baggage or carry on. Even if I can't setup a monitor and keyboard at the airbnb hotel. Having both off in lodging wifi is suitable enough.

Outside of html docs, it's purpose is similar to swagger

* Auto generate mock / containers for testing

* Generate server interfaces

* Generate models that go across the wire

* Remove boiler plate to spin up an async client, sqs, kafka etc.

That being said most of the generators are from the node sides and left a bit to be desired. I also see it falling into the same issue as open api. Most places I've been dynamically generate the open api spec.

I had written a JVM async/open api gradle plugin. That generated all the above. The nice thing was that if your server didn't implement the agreed upon spec it would fail to compile. Allowing for asynchronous development, back end/mobile/front end agree on the spec and can work on the feature at the same time.

This can also be expanded into k6/gatling. Hit this endpoint, guarantee this sla and ensure everything functions as expected. By having the contract first, you can automate a majority of the down stream tasks.

I think it has a use for contract first development, and is good in conjunction with something like avro. But it serves best in a contract first flow. Where in you define a spec, if it compiles you match the spec. Most servers don't take in a spec and define routes off operation names.

Why not dynamic async api generation? A lot of the generators reflect at run time, slowing down startup, and don't provide the most human readable definitions. Also lagging behind the latest implementation, and miss potential new features.

Been using Kotlin for ten'ish years. I feel the same, although I'm not part of the Java camp, coming more functional i.e. Scala. I was working on a number of open source libraries for a more functional reactive Kotlin, but have largely stopped.

They really painted them selves into a corner by doubling down on Spring, Micronaut etc. There is little benefit to those and Kotlin. From the back-end side, it's Java light, and Java has largely caught up.

If they kept to Ktor, Quarkus, vertx that could compete a bit with the Node/lighter crowd. Or people who limit class usage and focus on a more functional style. But that leads into that target audience...

Is not as apt to use Jetbrains projects, ancedotal observation. When I started Jetbrains was heavily used for python, ruby, etc. I converted several teams to Kotlin pre 1.0. But now with VS Code being the primary IDE/Editor, it's a much harder pitch.

The multi platform stuff feels half baked out side of UI. Having done several run time agnostic services, I hit so many road bumps. Jetpack compose is really cool though.

Where to go? This is an honest question. I just got done a project where we tried to go to Rust, and reverted due to wider difficulty with the borrower system across teams.

On another contract I spent several days tracking down node module resolution issues, and incompatibilities between peer dependencies. The script portion of package.json feels lacking compared to gradle and dependent task trees. NRWL/nx and Microsoft/Rush help a bit here.

I still feel Kotlin is a really good language, with graal if treated as Node with a better build system. But I rarely see that, mostly it's akin to J2EE or mobile.

Side question, is there a better remote desktop/spice client than Microsoft Remote Desktop via the app store? I've found it's performance lagging compared to MS RDP client, or Remmina on Linux?

They tried addressing some of the limitations of the JVM with native and co-routines. Making multi thread objects mutable, to not allow for race conditions. From a recent conference they backed off because they couldn't express immutability as a good idea.

I started multi platform with F#, Xamarin, and Fable. That worked, but F# doesn't have a wide community. The few F# teams I had been on we spent more time discussing mathematical proofs than delivering business value. I'm also getting to this point now, where I'm trying to build a simple SPA. I'm spending more time wrangling the tooling than delivering features. So that leads too.

I don't think there are good multi platform languages, besides JS. But I think we have a set number of transport means. Websocket, HTTP, HTTP2 to client, with various protocol, and content types. Back end say TCP, Kafka, MQTT, STOMP, etc.

I've been pivoting my focus from mp to schemas. JSON schema, backs async api, open api, and a number of others (aws cloud formation, github, gitlab, etc). With that schema you can now know the transport mean, and the object to be communicated. Additionally with the possible error responses.

The disconnect though is how are those schemas produced, and verified. Having a web framework generate usually results in badly titled methods, or a lot of additional cruft. I usually go contract first. But there are very few frameworks that take in and validate a schema. This leads to a disconnect, I've seen, where the server just doesn't match the schema. I had written a pojo generator for spring, that consumed a schema via gradle and output the response classes, and strongly typed the url paths. But it was met with a ton of resistance, namely because it wasn't maven.

If your back end consumes a schema, and starts the server. Then you know it adheres to the schema. This also allows for asynchronous development. Once the schema is finalized. Mobile, web, and back-end can all work on the same feature. As there are a number of stub container services, that spin up a service container used for integration testing, and generating out client SDKs. The few times I've been able to execute like this, it worked great.

Rust is a really great language. Having come from ocaml, it feels like a natural extension. My hesitation is two fold. One I have been using Kotlin + Intellij for ten years or so. I'd have to relearn a lot of my workflow, and port a lot of helper libs I wrote. Two I can never see using it professionally. All the Rust interviews I attended were white boards of algorithm, and calculus questions. I'm not a math person so that's not really feasible. I do want to take it for a spin in the future. Actix looks darn impressive.

This sort of echoes what I meant by in my opinion the build system is better on Kotlin, if not more complex. My opinion of course.

Using a library from a big tech vendor I found a number of issues with the definition files. That led to me tossing in ts ignore all over the place, and asking if I could file bug reports on company time. Lerna is the closest for a good multi module project. But that has a number of quirks.

As an aside I keep harping on multi module. But I find they really help with service boundaries, and flow of the application. Allowing dependencies to flow from bottom to top like a pyramid.

The other day I was working on a new proof of concept tool. I started with type script because that's what the team was using. But after cloning the demo from the vendor, it didn't minimize into proper java script. It seemed to be a known bug. I redid it in Kotlin in an hour. Because of the syntactic similarity, the team was able to pick it up. Worked on the first try. Now we just need to fix the TS build.

Incidentally these tooling issues are the bigger plague of the js multi platform. Dukat while great is only as good as the type definitions. There are also so many incongruities with the output. I've come to if I just output js I'm fine. But don't try consuming js. This also was the issue with rescript/reasonml to me.

I can output common websocket/http clients via ktor. Data classes, and other elements. But we have async api, open api, graphql, etc. The core of the multi platform driving business logic is being eaten by good automated tools. What's old is new.

I've been using Kotlin for a long time for backend/server dev personally and professionally. I've been feeling this more and more recently. I've said a couple times to my colleagues I've backed the wrong horse.

I had been making strong use of multi platform features. The end goal had been to easily move a piece over to a native image for server less if need be. Or output SDKs for Java script libraries. As an example I'm working on a multi platform micro-orm. But due to lack of cohesive reflection. I have to store the class package name in a map to reflect the type on all three platforms.

As to the note about inline types and Valhalla. Or loom for that matter. I have a feeling that will be buried as a compiler option. That needs to be amended in a build file. I have had to do this with JS, native, and a JVM

I'm finding that multi platform out side of mobile and JVM. Are not well polished. Additionally you're carrying a lot of baggage over from the JVM. In regards to it's type limitations and memory management. At the same time it's very impressive to easily target all three platforms. But it's a very difficult task.

Combine this with the few back-end places I've seen using Kotlin for the back end. Limit the features that can be used. To the end that the next Java version can primarily satisfy their needs. I've seen more effort coercing developers not to use sealed classes, null coalescing, co-routines etc. That could just be avoided by staying on Java.

I think it's a good language. It feels like a commonality of a number of the best practices. I've been able to migrate python, ruby, and typescript devs to a ktor setup and have them productive in a week or two. Gradle for all it's warts, I think is a pretty good build system. There is a rich eco-system of existing libraries. It has good performance, easy type semantics to grasp without getting in the user's ways. I feel like it's Typescript with a better build system (opinionated), and light pattern matching. The biggest API stability issue I've had is Gradle. I've carried projects from 0.11 to 1.4 with just nominal code base changes, but big build file changes.

The biggest focus is mobile, followed by Spring back-end. I have been very critical of Spring in my prior posts. There is a road map of Ktor, their in house web frame work coming soon. I'm curious to see where the language goes next. I'm finishing up one project in Kotlin but am eyeing Rust as a possible replacement

* Arch Linux / Manjaro. AUR is a great resource for the latest packages

* i3 / sway. I've built a number of custom patches on top of it.

* Windows Aero Snap - a close second

* MacOs - Yabai + skhd a very distant third. Mac doesn't just play as well with tiling.

* LibVirt / Virt Manager / CockPit / VFIO. I have a number of VMs emulating mac, windows, and linux. My workstation is all three in one. I also have a local kube cluster spun up via the libvirt api.

* JetBrains - Tool Suite They're tooling is phenomenal

* vim / nvim - My secondary editor for quick changes.

* Visual Studio Code - Primarily for remote sharing work spaces.

* Git - I keep almost everything in a git store of some sort.

* zsh and oh my zsh, great plugins.

* Kitty - terminal with the kittens plugins is great

* Direnv + EnvFile, dynamic loading of container env vars on entering a directory

* GitLab - Despite it's warts the best dev ops cloud agnostic platform I've used.

* Kotlin - I'm able to do pretty much everything in this. From vim over ssh or jetbrains. I use it for infrastructure, k8, mobile, web, and back end.

* Gradle - I curse at it a lot, but less than other build systems. I have templates that allow me to quick start any of the above templates.

* Remote Desktop - I keep a cheap dedicated server I RDP for heavy work loads while away from my workstation

* Reg Ex Pal - to validate reg ex

* Functional Programming

* Markdown / Restructured text - Great way to write docs and draft architectural plans

* MermaidJS, Lucid Chart - Easily embedded in markdown to provide graphs of architectural patterns.

* OpenAPI/AsyncAPI/GraphQL - Schema driven design let's me write the schema first, then generate type safe routes for the server, and clients for the consumers (web/mobile)

* Avro, Protobuf, Json Schema - For defining messages going across the wire.

* Containers - I started with solaris zones and it has been vital to my workflow.

* Docker Compose - This is the lowest barrier to providing a container stack for local dev. Next would be KIND.

* Docsify, Sphinx / etc. Easy way to add architectural docs next to the api docs as part of git pages.

That being said, I generally am unable to use a majority of these in my day job. So I'm operating much slower than I'm capable of.