cybrox (u/cybrox) - Readit News

cybrox commented on Sütterlin en.wikipedia.org/wiki/S%C... · Posted by u/anonu

yorwba · 3 days ago

If you carefully look at each word instead of mistaking the capital B for an L, failing to recognize the first word, and giving up in frustration, you can pick out common words like die or der and then slowly expand from there. It helps that one of the longest words in the text is Sütterlinschrift itself, which gives you quite a few letters. Once you have most of the alphabet deciphered, your internal language model takes over and it's smooth sailing from there. It definitely takes quite a bit of getting used to, but less so than e.g. Yiddish written in Hebrew script.

cybrox · 3 days ago

I second this. As someone who still learned "Schreibschrift" in school, I have a tiny bit of a head start but a lot of letters changed or at least changed in style drastically but I can reverse-engineer as you described.

cybrox commented on Why Elixir? Common misconceptions matthewsinclair.com/blog/... · Posted by u/ahamez

asib · a month ago

What part of the syntax is intimidating? To my mind, it's not all that dissimilar from e.g. Python, which is not a language about which people express the same feeling.

cybrox · a month ago

Structure and control flow feels very Python/Ruby-ish, however, when you get into the depths of pattern matching and binary deconstruction or even macros, Elixir syntax can become somewhat messy. However, the same concepts, once understood, are extremely powerful for parsing or protocol handling.

Talking about stuff like this:

      nodes =
        node_data
        |> Input.split_by_line(trim: true)
        |> Enum.map(fn <<
                         t::binary-size(3),
                         " = (",
                         l::binary-size(3),
                         ", ",
                         r::binary-size(3),
                         ")"
                       >> ->
          {t, {l, r}}
        end)
        |> Enum.into(%{})

cybrox commented on Why Elixir? Common misconceptions matthewsinclair.com/blog/... · Posted by u/ahamez

hangonhn · a month ago

I've been wanting to learn Elixir for a long time but is it worth learning it without knowing Erlang first? I'm not against learning Erlang but just curious if Erlang is a good thing to know before tackling Elixir.

cybrox · a month ago

We've been running Elixir in production for 5+ years and most of our team only know some very basic erlang data structures for working with the :dbg module on live systems.

Erlang knowledge is not needed for building products with Elixir at all unless you want to go very in-depth.

cybrox commented on I could not convince my k8s team to go AWS serverless medium.com/@dnsearching/h... · Posted by u/gpi

biot · 2 months ago

> Serverless Advocate: Yes, but instead of paying for infrastructure overhead and hiring 5–10 highly specialized k8s engineers, you pay AWS to manage it for you.

This argument lost me. If you’re running your own k8s install on top of servers, you’re doing it wrong. You don’t need highly specialized k8s engineers. Use your cloud provider’s k8s infrastructure, configure it once, put together a deploy script, and you never have to touch yaml files for typical deploys. You don’t need Lambda and the like to get the same benefits. And as a bonus, you avoid the premium costs of Lambda if you’re doing serious traffic (like a billion incoming API requests/day).

Every developer should be able to deploy at any time by running a single command to deploy the latest CI build. Here’s how: https://engineering.streak.com/p/implementing-bluegreen-depl...

cybrox · 2 months ago

Also: As if you didn't need "5-10 highly specialized engineers" (neither needs this number but alas) to get all AWS serverless services to coexist and scale cost and compute efficiently with proper monitoring, logging, permissions, tracing, etc.

cybrox commented on I could not convince my k8s team to go AWS serverless medium.com/@dnsearching/h... · Posted by u/gpi

moltar · 2 months ago

I can do all of the stacks well, including serverless described or pure ECS Fargate or Kubernetes.

From my experience Kubernetes is the most complex with most foot guns and most churn.

cybrox · 2 months ago

Is it? If you compare to serverless, you'd almost have to compare AWS EKS Fargate and with that, there's a lot less operational overload. You still have to learn ingress, logging, networking, etc. but you'd have to do that with serverless as well.

I'd argue between AWS serverless and AWS EKS fargate, the initial complexity is about the same. But serverless is a lot harder to scale cost efficiently and not accidentally go wild with function or sns loops.

cybrox commented on OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine github.com/stan-smith/Ope... · Posted by u/x0z

gtirloni · 2 months ago

This looks amazing. I find Mermaid.js ugly and the syntax difficult/buggy but unfortunately it's one of the best supported diagram tools in static site generators. It'd be awesome to have Isoflow diagrams embedded in Markdown like that.

cybrox · 2 months ago

I love the idea of mermaid but the syntax is somewhat convolutes and the integrations in tools like GitLab are very unstable.

cybrox commented on Apple's Liquid Glass is prep work for AR interfaces, not just a design refresh omc345.substack.com/p/fro... · Posted by u/lightningcable

swyx · 2 months ago

well then do it when it's ready, not before??

idk what it is but when a new paradigm comes whether it is AI or AR the bigtech companies always want to ram it down everybody's throats rather than gentle opt-in. its not like they lack enthusiasts who WILL opt in to offer feedback.

you have billions of users, including many normies who just want to get shit done and dont even know that you have keynotes or shareholders to impress and dont care about the translucency of your "glass" when they're trying to call 911[0]

[0]: see talk (https://meyerweb.com/eric/thoughts/2016/01/25/designing-for-...) and tldr (https://hookedoncode.com/2015/02/designing-for-crisis-by-eri...)

cybrox · 2 months ago

Changing the UI beforehand is their approach at a gentle introduction. It's just not voluntary.

cybrox commented on Nextcloud cries foul over Google Play Store app rejection theregister.com/2025/05/1... · Posted by u/brodo

cybrox · 3 months ago

Maybe a fluid, touch-centric experience would be less important for most use-cases if not every simple to-do app had to be over-engineered with 20 animations and gestures...

cybrox commented on Top employee monitoring app leaks 21M screenshots on users techradar.com/pro/securit... · Posted by u/mooreds

cybrox · 4 months ago

My sympathy for companies that decide to employ such tools is very limited.

cybrox commented on Microsoft’s original source code gatesnotes.com/home/home-... · Posted by u/EvgeniyZh

mindwok · 5 months ago

To be fair they definitely faked it, they said they had source code for a program they hadn't even written yet! They were just also very serious about the "making it" part.

cybrox · 5 months ago

True but "fake it and then immediately proceed to make it" is definitely more appreciated than just burning through deals by lying for a long time, which "fake it till you make it" usually boils down to.