Siri+
1,397 karma · joined March 15, 2015
My posts and comments do not reflect the views of my employer.
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)
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?
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.
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.
Check out Vercel, Fly.io, or DigitalOcean depending on the complexity of the project you’re hoping to deploy.
They don’t have these checks in place for the fun of it. They’re usually legally mandated, otherwise some parent will sue them because “Google exposed my child to X Y or Z”
[1] https://support.google.com/families/answer/7106787?hl=en
I even have it configured so that ports can be routed to via my domain, meaning I can do web development with a local server on port 3000 and view it live at 3000.my.domain.tld.
I’m absolutely a fan of engineering feats like these being made more accessible for educational purposes. Even in college, I built a NES emulator on an FPGA.
But to argue that it’s primary motive is not to facilitate (and potentially profit from) piracy is not grounded in reality.
They are seeking returns on this investment in the magnitude seen in previous YC company IPOs, as mentioned in the article. Is a bootstrapped company likely to have that outcome? Possibly, but much less likely than those that have swelled with additional funding rounds and more rapid/predictable public interest.
Any employer that expects otherwise should be avoided at all costs. Admittedly, even this is not entirely full-proof, but it is the bare minimum.
JS/TS are used in the Terminal's view layer. You can make services in these languages as well, AFAIK, but I don't think it is very common.
I helped many teams move from Java to Go, and came across this so many times. Everyone wanted to find the Spring equivalent for Go (or Django, Ruby on Rails, etc) when it doesn’t actually exist. That’s by design.
No ill feelings toward the developers of Echo, or other similar frameworks (Go Micro specifically). However, touting their framework as the way to build APIs in Go is disingenuous and leads to software that is difficult to maintain.
Just my two cents.
These languages - I would throw Swift in there as well - are “apples and oranges” and shouldn’t really be compared. Depending on your use case, they all have different merits over each other.
To actually make a worthwhile recommendation, you’d have to elaborate on what you mean by backend service. RESTful? gRPC? Something else? When it comes to the first two scenarios, I think Go enables more rapid development and has a stronger library ecosystem.
Specifically, I think it would help for them to verify ads, as they do people / pages.
Hoping other platforms follow suit. Preferably using SwiftUI...hey, I can dream right?
My only question relates to payment. This is an app that I would gladly pay a solid price to own (in the ballpark of $50?). I would _much_ prefer that over a subscription model.
Because the site mentions eventual payment, but doesn't specify a pricing model, would you be willing to elaborate on your intentions?
Also worth mentioning is ORY Hydra.