losingthefight

I run OSS Grafana with Loki, Prometheus, and Tempo. I use an Alloy sidecar taking in OTEL and scraping logs.feom my Go services and selfhost the stack. Once you need to scale it gets a bit more complicated but it's all still OSS.

The biggest challenge I have is that each data source needs it's own query language, which DD and the like don't. That's why at my day job they went with DD despite the costs. Still OTEL but the querying is the same. We are also looking at Dash0 but for all of my personal and consulting jobs, OSS LGTM/P works good for me.

I couldn't disagree more. Compared to the mess of hooks in React, Svelte is closer to JavaScript in the script portion and closer to normal html in the markup portion. I use vite and TypeScript with each project and never once had a typing issue. Ive built several production apps and consider it far better for my brain than other libraries I tried, and I've been using React since before Redux was mainstream. Svelte is my go to now.

I see this argument a lot, and I think it's fine if not a tad flawed. If that's what you want, you can keep it. I don't really see anyone saying "kill the review process" and "open everything by default". This would all go away if Apple simply made it a setting to allow other IPAs AND allowed outside payment / subscription management. Keep the garden if you want it. Don't enable outside installs. If you don't want to support a company not using Apple Pay and the like, then don't! You're the consumer! The difference here is Apple doesn't give you a choice. Even if the developer does all the legwork to build a payment system (for example, they have a web app as well) and market the app on their own, they have to give Apple their cut. You don't get a choice and neither does the developer.

Wagz | Senior iOS Engineer | REMOTE, US Only, New Hampshire / Massachusetts Preferred | Full Time | https://wagz.com

Do you want to help improve the lives of pets and their families while working on cool technology? Come join the Wagz team!

Founded in 2015, Wagz is a pet-technology IOT company aiming to better the lives of pets and their families with innovative technologies. Our vision is a fully-connected pet lifestyle with a suite of devices that give owners complete insight into their pet's lives.

We are currently looking for a Senior IOS Engineer. You should:

- Have senior-level experience working in IOS using Swift, bringing apps from start to production - Have a deep understanding of IOS design patterns - Know or be willing to learn how to design user interfaces without storyboarding - Possess an understanding of Continuous Delivery / Continuous Integration, including automated testing, beta testing, and app store deployments - Have an understanding of Bluetooth, multimedia, and related technologies - Be a self-starter, motivated, and able to work remotely effectively

Wagz is located in Portsmouth, New Hampshire, but we are willing to consider remote candidates in the United States. We do not offer sponsorship. No agencies or organizations. This is a full-time salaried position.

Wagz provides great benefits and the opportunity to grow and lead within the company. Interested? Send your resume to [email protected] !

I am going to disagree pretty heavily with this. You don't give any explanations, evidence, or mention your experience, so let me lead with mine before I explain where I think you are wrong.

I cut my teeth in the 90s with C, and have professionally used PHP, Python, Java, C#, Javascript (both server and client side), and have been using Go as my main choice for the past 4 years. I've worked on teams as small as 1 up to teams in the hundreds, both as an individual contributor and tech lead. I say all that because I would consider myself an "experienced programmer". I am mostly writing APIs for web and mobile apps to communicate with, although I have written code in a wide variety of contexts. I say all of that because I can't imagine going back to Java or Python. I even migrated a bunch of my services from Typescript to Go because I found Go to be far more productive and easier to work with. Refactoring as always been easy. At my current job as a Chief Software Architect, I have over 25,000 lines of code in production running Go. I say all of that to provide background and context on my humble opinions.

1) Verbosity is among the leanest I have seen for a type-safe language. Compared to Java or C#, it is much more like Python. Perhaps the most verbose sections are a repetition of "if err != nil" blocks, but those are there for a reason and I explicitly prefer that over long "try catch" blocks.

2) Not sure what you are arguing here. If you are talking about functions returning multiple values, many languages do that. If you really don't want to, return a struct or a map. Or choose to not return multiple values. That is a choice of the programmer, if I understand you correctly. You could also use any of the major editors (I prefer VS Code) to refactor; the tooling is awesome (see #5)

3) Maybe it is due to the nature of what I do, but I have never once thought "man, I wish I had generics for this." I am sure there are some who genuinely need it, but I haven't run across that in my own experiences. I find that structs and interfaces have been everything I needed there, but again, my use case is on the server.

4) I haven't needed to use reflection either, so I have no comment here.

5) Hard disagree. GoLand (by Jetbrains) and VSCode are INCREDIBLY powerful. I will never go back to Eclipse or Visual Studio if I can avoid it. Go ships with tons of tools (formatters, linters, vetters, etc) and integrate with a ton of others (delve, etc). So your statement simply isn't true.

Your last statement is probably what drove my response. I was able to spin up a full API server incredibly quickly alone, and then with one other person, in a fresh startup with minimal issues. Rules and requirements were changing daily, so the code and business logic had to change. I can't imagine having to do that kind of work in Java (don't get me started on the deployment story here...). I would argue Go is a great fit for small teams. It is a small language with opinions, so programmers can focus on their use case.

Go isn't perfect, but it's my tool of choice. That's my two cents though.

My youngest daughter was born with it and strangely enough, my wife was diagnosed with it a few years after she was born. Neither I nor my oldest daughter have it. Both of those who do have it were confirmed through several tests with the doctors.

We are lucky to be alive now rather than, say 20 years ago. Gluten-free and celiac-friendly foods are readily available in the US. We live in New Hampshire and most restaurants and grocery stores have a wide variety of options. I know it is better in larger cities, but most places are pretty good, and we have a few favorite restaurants near by that take it very seriously.

The hardest part, honestly, is at home. It is too easy to forget I made my oldest daughter a grilled cheese and therefore have gluten crumbs on my fingers. I then touch something my youngest is going to eat, like getting her some chips or fruit, and I accidentally contaminate her. We've gotten better over the years (she's 12 now) but it still takes a lot of work and discipline.

Overall, though, it's not nearly as bad as it used to be. I know some older friends who have Celiac disease and they would talk about how hard it was to find anywhere to eat out and how expensive things used to be (although, they are still expensive now).

Still though, it would be great if there was some technology to identify cross contamination or, even better, some medication that would prevent the reactions. It would be awesome to not have to worry about the implications.

For reference: my daughter with Celiac is a top-notch gymnast (yeah, dad brag and all, but she legitimately always places in the top 5 at every meet). If she gets cross contaminated though, she can barely walk in a straight line and her focus is way off. It has a real, noticeable impact.

I mean, this isn't really true though. If you forgot, you can have your JWT middleware check and if the field is missing, revoke it. There are tons of workarounds here and I have implemented them in several consulting roles. I personally always put a created and expires timestamp, bit if they aren't there, there are ways to fix the situation easily.

I personally make it clear that side projects, monetized or not, are one of the best ways to learn new skills, ways of thinking, and improve productivity. I agree to sign non-compete and clauses stating that anything done outside of the business requirements (I don't work hours, I work results kind of thing) will not conflict with, impede, or otherwise negatively impact my position. I've only had one employer in the nearly two decades that had an issue with that, and ironically it was an organization that had pretty high turnover from the reviews I read.

Whomever is paying me is paying me to do a job. They don't own my life, my free time, or my hobbies. If they don't understand or support that, I wouldn't bother going forward with them as it's simply not the kind of culture I would want anything to do with.

Also, to the person who wrote about external income needing to be documented with a ton of paperwork... if you are in the US, what about US Reserve military members (which is a protected status)? Adjunct faculty positions? Seems like the employer should not have any say on that kind of income.

I mean, everyone is entitled to their own opinion, but I actually liked dep and never had a problem with it. With Go modules, it has been a massive problem converting our microservices over to Go modules, especially because some dependencies like Resty caused a lot of headaches and I lost several man weeks going through the process. Dep worked and modules doesn't seem to have brought us any real benefit, but again, my use case is my own and perhaps for you module was a better experience.

Aside from what others have said, the single tiny binary and cross-environment compilation is a huge plus. I can compile my largest service in seconds for Windows, Linux, and Mac (we still use Docker, but not for the cross-environment reasons). It's simple, concise, and fast out of the box. I also have been bitten far too many times by the JVM being RAM hungry and, frankly, I focus on startups which don't have time or resources to spend tweaking VM variables. Granted, I am sure Java and the JVM have come a long way since I last used it heavily in 2013, but I haven't found a single reason to want to go back.

As far as Python, same kind of reasons. Single binary makes deployments easy, static analysis and built in tooling makes life easier, and I just find it more enjoyable, which is completely subjective.

Sorry if I wasn't clear. I don't really combine the two and use whichever makes the most sense. In my day to day, we are primary a Go microservices shop and are exploring Elixir for some video stuff. I've used some Elixir on side projects. Sorry I wasn't clear that I am not combining them, although I imagine if I was going to it would either be over some sort of gRPC implementation or using something like rabbit to hand over tasks.

I have been using Go in production since 2015 and can honestly say that other than the ternary operator, none of these have been a major issue for me. Granted, I am doing mostly REST API development so my use cases may be different, but I have never had an issue with capitalization or which interfaces are implemented. The tooling is by far some of the best I have used in a language. Paired with a good editor (I personally use VS Code on Ubuntu 18.04 as my main setup) and I have yet to miss exceptions or wonder what my code is capable of doing.

That being said, Go isn't perfect by any stretch. Sometimes panic ins Go routines can be very hard to trace. The transition to Go modules is challenging for larger projects with versions beyond 1.x (when I started it was Glide, then dep, now go mod, which has been a bit frustrating). However, I wouldn't go back to Java, C#, PHP, or NodeJS if I had the choice.

My go to in the server space is Go and Elixir. I don't feel a desire or need for anything else, but again, that's me. You know your use case better than a stranger on the internet :)

Really? I mean, pick one of a hundred. They are deprecating APIs that would block the interception and are ignoring community pushback.

But since you asked...

https://bgr.com/2019/05/31/google-chrome-update-ad-blockers-...

https://www.vice.com/en_us/article/evy53j/google-struggles-t...

https://9to5google.com/2019/05/29/chrome-ad-blocking-enterpr...

But I mean, that was a 2 second search. Citations are indeed hard to come by...

Wagz | Portsmouth, NH or potentially Salem, NH | ONSITE | Full-time

Wagz is a state of the art pet-technology startup with an office in Portsmouth, NH. We are exploring a second office north of Boston, MA in Salem, NH as our time is growing dramatically! We are looking for senior Android, IOS, and Go Software engineers to come help us revolutionize the pet IOT space. There are several positions available.

You will have the chance to work on a variety of new technologies, including (but not limited to) Android Things, AWS IOT, native Android and IOS apps, server-side Go, and more. We have three products on market and three more scheduled by the end of the year. We offer a great package of benefits, including the ability to work offsite several days a week, health, dental, vision, life, and a "take vacation when you need it" policy.

I personally conduct the hiring process, so if you are interested, send an email to [email protected] and let's see if we're a good fit for each other!

Not OP but maybe he is referring to the big in which the npm upgrade bumped to a non-ready version and caused havoc on production systems by overwriting permissions and files: https://github.com/npm/npm/issues/19883

That was the end of February, so not sure but that may be it.

Looks like they won't: https://twitter.com/SlackHQ/status/925586114152411137

We've no solid plans right now as we're focused on tidying things up internally, but will consider it. Thanks again for holding tight

So, I totally read that title as "Cisco's feud with Former Star Trek Executive Turns Personal and Costly", thinking they misspelled Sisko from Deep Space 9. Been a long day...

Could you provide a demo of some sort on the landing page? I have been writing APIs for over a decade and still have no idea what benefit this provides. Who does it compete with? What differs it from a starter/seed project? Do I still write code or is it a visual interface? What sort of redundancy and reliability does it have, especially since I haven't heard of the project or company before?

$20/month is a bit much for a side project. For a real world project, the price is peanuts if the benefits are there, but the lack of explanation makes it a non-starter for many companies, I would imagine.

Luckily, most of that seems to be marketing and documentation, which shouldn't be too difficult to update, if the product is working correctly at least.

Unless he isn't an atheist? Plenty of theists can hold to evolutionary views or intelligent design.

Further, the language choice could be colloquial in which case he wasn't trying to make a theological statement; rather, op used common phrases to convey the relevant thought. not sure we need to push a worldview here...

I don't think this is reflective of most consumers in the US. I have a family of four. I couldn't imagine the kids working on school work, watching Netflix, or gaming while I try to teach online all while on a WiFi router connected to DSL. While it may work for you, the fact of the matter is that it likely will not work for many, hence the reason Comcast can get away with this crap (well, that and the monopoly).

I have joined a few startups and architected a few as well. I currently love one of the following two stacks, depending on the need:

GoLang -> Postgres -> React Meteor -> MongoDB -> Blaze

Of course, most of those are interchangeable. We use Redis for caching, Docker/Ansible for deploy, etc.

I completely disagree that Apple is not at fault here. It should always prompt, end of story. More importantly though is that the devs at FB, Google, etc, likely saw how it worked in mobile Safari and, wrongly, assumed it would work the same in a webview. Why have the inconsistency in an a tag?