Readit NewsWe could ignore this repo and construct our own project structure based on our requirements.
As someone who has worked with Go for years in a professional capacity, more than half of these folders are not necessary or convention in any sense. They usually introduce complexity into a language and ecosystem that tries very hard to prevent it.
Folks reading this without Go experience, really the only ones that are important are "internal" and "vendor" folders. The former cannot be imported into consuming packages, and the latter is the output of "go mod vendor" (commonly required in corporate environments). "pkg" is also mostly a convention because of projects like Kubernetes, but is not idiomatic either. (A Git repository itself represents a Go package or collection of packages based on the presence of a go.mod or go.work file)
But I still got a reminder that this show was available when I asked what time it was the other day.
Shame the amount of engineering effort that went into that system, only for it to be destroyed by absurd business strategy. I’m sure a couple PMs got a “level 2 to level 3” promotion out of it or something.
Why would you want to loop in a completely separate service when GitHub and Jira already have an integration available?
This is definitely a step up, nicely convenient. But also, it has downsides too. gRPC is incredibly well supported by a huge number of observability tools and service-layers/service-mesh systems. Few have support for gRPC-Web. Which if any have support for Connect-Web?
In general, it's just massively sad that the browser never got around to making HTTP Push useful for protocols. gRPC should have been positioned to do great things, was a very common-sense overlay atop HTTP2 that provided just a little more semantics to say how things ought work. It triangulated nicely on where we were going, at it's inception, back in 2014/2015. But the browser basically never evolved, never gave developers access to do the good stuff we thought we'd start to have access to. I still see brand new specs that shout out to the Low Level Extensibility Manifesto[1], but for some reason, in terms of the most base layer of the web, HTTP, this simple guidance has been roundly ignored & the capabilities were never delivered. So gRPC has been stuck with a pretty ok protocol, & frustratingly discompatible browser.
1. Embrace gRPC and protobuf 2. Extend with Connect, get everyone using this in their APIs and web apps 3. Drift away from established gRPC and/or protobuf standards, build platforms/business around this and trap as many folks as possible
As silly as it may seem, one thing that really sends this signal for me is the nice trademark symbol on the Buf name. their intention for all of this stuff is to build a business.
One thing that stuck out to me was the “Our technology partners” section. Is Theos actually “partnering” with companies like Google, Meta, Nvidia, OpenAI, etc, on anything? Or is Theos just using technology from these companies? If it is the latter, this seems very misleading.
Nonetheless, hope it pays off for them.
The problem is, X and Y have different line heights and different widths. And there's no CSS / media query way to detect which font is available.
So far I'm leaning towards a very ugly solution: rendering a test string into a DIV, measuring it, and then applying the correct class to the parent element.
If you want to align the text vertically with an image, use flexbox. If the specific font they want to use doesn’t look right in that context, have them either (1) deal with it or (2) pick another font.
But you don't need to beat chat-gpt 4. A chat-gpt 3.5 esque model that has access to your todo list and calendar that I can talk to like siri would make the tool 10x more useful overnight.
If it even had access to your last 50 emails I could imagine saying something like.
- remind me to respond to that email from bob tomorrow.
- Draft me 3 responses that are kind, but indicate clearly that we can't go forward with his request.
This could even happen in the background, and I'm happy to pay a bit extra for the compute, it could be "premium siri"