Recently I used Google maps to search for the nearest DHL near me so I could return a package. DHL is not that popular near me and when I specifically typed for DHL, I would get only their competitors in the search results.

There was a DHL service center near me and I had to scroll a bunch to find it. Oh, and apparently big box stores (or anyone) can pay Google to come up in the search on maps, even if unrelated.

I don't think they have skin the in shipping game but their algorithms are over optimized that they don't even show what your searching for, but trying to infer why you're searching for it. That or whoever pays them more. Certainly a search risk

Out of college I did not work at a start-up but instead got a job at a "big, stable" corp. I got the following advice from the older engineers at big, stable corp. Some of those engineers are my personal friends 7 years later.

"Why work here where it's slow and stable? You're young, go take some risks, earn money, and most importantly get experience under your belt. Then come back with experience and coast. Your compensation grows slowly here so might as well come in with experience and start with a high salary. Also, everything is slow here, your peers at fast paced companies will out pace you."

That was some of the truest shit I've ever heard. I've since left big,stable corp and am working at a company who was a start-up but opted to grow instead of being bought out. I am working on a family so cannot afford the risks of a start-up.

Yes, I work many more hours but the pay is way better and in the last 1 year I've learned more than i've learned at big,stable corp. There is just much less process and red tape and we are more hands on and wear many hats. At times this is exhausting but I find comfort that if I were to lose my job, I have tangible experience to get hired again where as at Big,stable I was picking up skills how to do reviews on processes and techniques unique to the company.

when running models locally, I presume the models are trained and the weights and stuff are exported to a "model." For example Meta's LLama model.

Do these models get updated, new versions released? I don't quite understand

wow 10 months flew by since this was posted and since then the United States had a surprise privacy bill that is bipartisan that sort of addresses the issues you and I mentioned. https://www.washingtonpost.com/technology/2024/04/07/congress-privacy-deal-cantwell-rodgers/

This bill was proposed around the same time the TikTok ban was announced. I speculate that law makers had a difficult time framing the arguments against TikTok when "the data of citizens have no protections so there was no easy legal grounds to forbit the likes of TikTok to harvest it"

From what I've heard, this bill is pretty good. I need to educate myself more on it, however.

was it ever? I participate in interview rounds at my company (several tech screens a month) and I must say a candidate's email was not something that drew attention

you're able to unsubscribe from all those protomtions . . . that is in settings. Personally, a once-a-month newsletter of everything that is new is helpful bc I don't need to put in the effort tlinto keeping up

For backup and sync I use Syncthing. I can specify which folder on which devices I want to sync to which folder on the server.

I use a folder based gallery on my phone so when I move stuff around on my phone (or on my server) it gets replicated on all my devices.

I also have a policy to sync specified folders (and subfolder) with my family's devices. No more " hey can you send me all the pics from the XYZ trip"

We take a trip. Make a subolder for that trip in a shared folder dump all our pictures there, get home and open the folder on the computer and prune together.

simply put, programming is glorified automation. There are jobs where the process that needs automating makes money.

Debian has the advantage of not using snapd like Ubuntu does. You have to not only remove snaps but also instruct the package manager not you pull in snaps as dependencies and not to favor snap packages.

I have fond memories of Ubuntu being my first distro many years ago but pushing snaps onto users to compete with flatpak is a nuisance.

I don't think I am well positioned to answer that question given my experience. Ill give it my best.

I believe the advantage of more abstraction of gRPC was desireable because we can point it at a socket (Unix domain or internet sockets) and communicate across different domains. I think we are shooting for a "microserves" architecture but running it on one machine. FFI (IIRC) is more low level and more about language interoperability. gRPC would allow us to prototype stuff faster in other languages (like Python or go) and optimize to rust if it became a bottleneck.

Short answer is, we are able to deliver more value, quicker, to customers (I guess). But I don't know much about FFI. Perhaps you can offer some reasons and use cases for it?

At work, we started the c++ migration to rust doing the following:

1. Identify "subsystems" in the c++ code base
2. Identify the ingress/egress data flows into this subsystem
3. Replace those ingress/engress interfaces with grpc for data/event sharing (we have yet to profile the performance impact of passing an object over grpc, do work on it, then pass it back)
4. Start a rewrite of the subsystem. from c++ to rust
5. Swap out the two subsystems and reattach at the grpc interfaces
6. Profit in that now our code is memory safe AND decoupled

The challenge here is identifying the subsystems. If the codebase didn't have distinct boundaries for subsystems, rewrite becomes much more difficult

hey, that's what the internet is for; information sharing :)

for the dummies (like me) that can't read the room, especially online, a sarcasm tag /s goes a long way 🙃

you sound like a Microsoft engineer ;)

I agree with the sentiment but Google is an Ad business. Selling phones by itself does not financially support them.

GrapheneOS on Pixel is the most stable and secure way to have a modern mobile phone that is free of trackers (from google and apple alike).

I can't picture a better way to "stick it to the man" than 7 years of them unable to track and serve you ads

hahaha good point.

That colleague, keep in mind is a bit older, also has Vim navigation burned into his head. I think where he was coming from, all these new technologies and syntax for them, he much rather prefers right clicking in the IDE and it'll show him options instead of doing it all from command line. For example docker container management, Go's devle debugger syntax, GDB. He has a hybrid workflow tho.

After having spent countless hours on my Vim config only to restart everything using Lua with nvim, I can relate to time sink that is vim.

Had a distinguished collegue (from the Bell Lab days) say to me recently:

"IDEs take up a lot of RAM on my machine. Vim takes up a lot of squishy RAM in my head. I need squishy RAM to hold info relevant to problem solving, not options available in my tool chain."

As a former Vim user myself, I have to say I really dislike screensharing with coworkers who use Vim. They are walking me through code and shit pops up left and right and I don't know where it comes from or what it is I'm looking at. Code reviews are painful when they walk me through a large-ish PR.

These days, I tend to bring my vim navigation/key bindings to my IDE instead of IDE funcs to Vim. Hard to beat JetBrains IDEs, especially when you pay them to maintain the IDE functionality.

code is just text, so code editors are text editors.

What sets IDEs apart are their features, like debugger integrations, refactoring assists, etc.

I love command line ± Vim and used solely it for a large portion of my career but that was back when you had a few big enterprise languages (C/C++, Java).

With micro services being language agnostic, I find I use a larger variety of languages. And configuring and remembering an environment for rust, go, c, python etc. is just too much mental overhead. Hard to beat JetBrain's IDEs; now-a-days I bring my Vim navigation key bindings to my IDE instead of my IDE features to Vim. And I pay a company to work out the IDE features.

for the record, I am in the boat of, use whatever brings you the greatest joy/productivity.

wait until Google releases a new pixel this fall, buy "last year's" pixel at a discount and they are supported for 7 (?) years of updates (including firmware).

I would recommend GraphenesOS bc they only deal with android and pixel phones so there is a high level of compatibility and things rarely break. (In many cases GrapheneOS was more stable than Google's android, recently with the multiple profiles and memory bug). They also push fixes and security hardening upstream sometimes.

Anyway, GrapheneOS will support a Pixel for as long as the manufacturer (Google) releases firmware updates. So you have the potential of 7+ years of support from GrapheneOS.

I can always get behind a more open platform, but what is the appeal of codeburg over github?

EDIT: gitlab is also an option. Many companies use it internally and you can also have external accounts

How exactly does this make apple look bad?

sincere question, I am layer 3&4 network stack developer so I am quite out of the loop for mobile apss/web tech

don't insult children like that.

Yeah I was not a fan of paying for Spotify and them cramming ads of podcasts down my throat when I wanted to listen to music. Plus their shuffle is a joke. Music discovery was pretty sweet though

Hard Fork: for keeping up with the biggest tech news. they do dissecting of potential impact if stuff.

Lex Fridman: He interviews really interesting subjects. I'll listen to subjects I'm interested in based on who they are or the subject matter they are an expert in. Lot's interesting tech folks. My favorite episode so far is with John Carmack: Doom, Quake, VR, AGI, Programming, Video Games, and Rockets. Epsidoe is 5 f***king hours but broke it up into several sessions and Carmack is so good in articulating, it flew by.

Huberman Lab: before software I liked biology and medicine. I like these occasionally because I get to learn how systems outside of software/hardware work. These I will watch/listen in a sitting as one would to a movie. It demands your attention to follow along. (I don't like when doctors have podcasts with all the "alternative medice" BS. But Huberman is an active researcher at Stanford and in charge of a lab that cranks out sweet research. Def credible dude and very methodic and tries to rule out bias).

You can still buy a lifetime licenses of office but you have to buy it from 3rd party sellers and then validate the license with M$. Example Deal..

I bought 2 of them and also saved the install binary to have office suite.

I use libreoffice personally but I have family members that get frustrated when they cannot find the same formatting options

newsblur

I tried Logitech's wave keys at the store and I fell in love with them. I have several custom keyboards (including a HHKB with topre keys and WASD Code keeyboard) and this puts them to shame, unfortunetly. Can pick it up for $56 USD.

https://www.logitech.com/en-us/products/keyboards/wave-keys.html

• The shape is not those crazy ergo keyboards but the keys are very easy to reach, and you will not have to adjust to a new layout if you are comfortable with laptop keys.
• The keys have more travel than laptop keys but less than mech keyboards (on average).
• The Keys are also effortless to press but offer resistance.
• Bluetooth and if you use wireless Logitech mouse you can use the same BT receiver.
• They have them at Staples and Best Buy, so you can go and try it out.

As for programming, I found the WASD Code keyboard to be pretty customizable with their hardware switches. I can flip a switch and boom, my Caps Lock is now another Ctrl, etc. But you can do that in the OS as well. They go around $99 and you can pick different keys. Not sure if they have any wireless ones

https://www.wasdkeyboards.com/code-v3-87-key-mechanical-keyboard-cherry-mx-blue.html

I always thought about this. What about those with disabilities, like ADHD? Can companies really maintain their "equal opportunity employer" position while stripping privacy in the workplace? That's an over generalization for moving to an open office.

They will make a few exceptions then at some point say "that's enough" when all the employees need is less stimulation and more privacy

People like having choice, it was never about saving space in phones.

If you look at which company (apple) and the time of removal of headphone jack (around the time their wireless buds were announced), you'll notice they removed choice so the consumer can only buy more expensive wireless buds, or many many dongles.

The "save space" is an absolute lie. The international (EU, Asia, etc) version of the iPhone has a dedicated SIM card tray. The US model? No tray, just a freakin placeholder where the international version has the SIM tray. Yes, there is a volume of space that can fit 2 headphone jacks on the US iPhone that is just empty.

Look at this iFixit video where they call apple out on it. The placeholder is huge. at ~1:17+

cool thanks.

Well I'm glad to hear these things being worked on and worked out

I see. That's a good question because I'm not even aware of other "orchestrators" outside of kubernetes 😅

I agree that by design Flatpak aims to provide a secure environment through sandboxing; in practice, the implementation has gaps that can lead to security risks, particularly when apps are granted extensive filesystem access. This can undermine the effectiveness of the sandbox and potentially expose systems to vulnerabilities. HOWEVER, being on an immutable system, these risks are mitigated to some degree.

I'm particularly hopeful for Flatpak's promise of fine grained permissions. Flatpak is developing a fine-grained permission system with portals for external interactions, BUT this system relies on integration with toolkits like GTK, rather than app-specific APIs, complicating its implementation. There is more info in the linked article in the previous post, and here it is again.

Admittedly I'm not familiar with distrobox, but my caution is for any approach that distributes containerized programs with their own runtimes; they proved to be a real headache on my "mutable" system and my nvidia GPU until I switched to rolling OS.

I'm glad you found some candidates to potentially resolve your issue. What distro did you end up using? I'm curious to give it a go next chance I have some free time. Cheers.

TIP: programs that run inside docker containers should be compatible with the host system's kernel.

If you want to run a container targeted for a linux distro on windows, you need some intermediate that will translate Linux sys calls to windows ones. I don't have experience with this but I believe that's what WSL accomplishes? Among other things.

Regarding your question about lock-in, if I understand it correctly, you are targeting the kernel really, thats the "engine". So "lock-in" is about the same as you choosing which OS to target.

TL;DR: If I were to choose an immutable OS to run on my propriety graphics cards I'd choose an immutable distribution with rolling releases or hardware enablement packages, which tend to do a better job of keeping these graphics libraries up-to-date for new hardware.

I don't have a recommendation but I just learned about immutable Linux OSes from this post. I could see benefits of immutable OS files, but I've been skeptical about package distribution like flatpak and snap, at least in their current state.

Dont get me wrong, the workflow of flatpack is great, but in my experience, apps from flatpack typically ship with their own runtime and don't rely on system runtimes (likely why you have GPU driver issues). As a software developer, I obviously prefer to ship with all dependencies and runtimes so I don't have to rely on the system to be updated but this comes with downsides:

A major problem with alternate runtimes is drivers. New graphics hardware needs new graphics libraries which have a ton of dependencies. Mesa depends on LLVM for compiling shaders. The NVidia driver depends on a kernel module whose version must exactly match that of the library. All of these libraries have their own transitive dependencies like libdrm, libstdc++ and glibc. If you want new hardware to work, you need to be using new versions of all of these libraries.

Linux distributions, especially those with rolling releases or hardware enablement packages, do a great job of keeping these libraries up-to-date for new hardware. Bundled runtimes do not. Source.

I'd recommend checking out that article I linked as source. There are also security concerns of using apps, some of which are mitigated by having an immutable filesystem, but there are more points and this comment is long enough as it is.

EDIT: I reread my comment and it comes off as "immutable bad, blah blah". Truth is I don't know much about these OSes but I wanted to point out that distributing apps in containers comes with its own challenges; which I gather is necessary for immutable OSes. So my TL;DR is to narrow down to a distribution that is immutable and has a rolling release or distributes hardware enablement packages.

The statement is very informative. The bug happens under increased read/write operations to the same file causing a race condition.

I also found interesting:

Despite the bug being present in OpenZFS for many years, this issue has not been found to impact any TrueNAS systems. The bug fix is scheduled to be included in OpenZFS 2.2.2 within the next week

I'd really want to know what's driving them

likely ego

I heard in their Q3 2023 quarterly earnings call that 6 years ago they left a PCIe slot free in every server so they could accommodate upgrades in the future as they grew. They were suspecting it'd be with the boom of AI/graphics cards but didn't want to commit to it yet.

Now they are plugging up that empty PCIe slot with newest gen graphics cards with their launch of Workers AI.

This is cool because they had foresight to make an uncomfortable decision initially but were able to respond to their growth objectives without spending capital expense to upgrade the entire servers.

Their recent blog on the design of the new servers is mostly around temperature, efficiency, and rack density. So unfortunately no hints at what's to come.

This is interesting. Don't have an opinion on it yet.

I wonder what effect this will have on developers' code reuse practices and how it comes across in the interview.

At work I often look at my previous work for how to do boilerplate stuff. And in my recent interview experience I had more opportunities to use the internet and other examples. Very practical

When I was in college, two older classmates whom I respected got into a hilarious argument of why Gnome was awesome and now eats rocks (their views, I had no views).

Their elaborate and very specific descriptions of functions and inconveniences drew up a picture of functionality and a e s t h e t i c I had never experienced on windows. So I proceeded to install a distro and take it for a ride