The Party Package: Fill & Download for Free

Hello!Schaden meet freude. The Wisconsin Republican Chairman returning from a tropical vacation on his new private jet said that the money was stolen by ‘hackers’. Oopsie, wrong line here…I suppose.Anyway Bloomberg reports:“the hackers manipulated invoices from four vendors who were being paid to send out direct mail for Trump’s reelection efforts and to provide pro-Trump material such as hats that could be handed out to supporters. Invoices and other documents were altered so when the party paid them, the money went to the hackers instead of the vendors.”“The party noticed the suspicious activity on Oct. 22 and contacted the FBI on Friday, said Republican Party Chairman Andrew Hitt. He said the FBI is investigating. FBI spokesman Leonard Peace did not immediately return a message seeking comment.”Wisconsin Republican Party Says Hackers Stole $2.3 MillionHow does Hillary find the time to drink baby blood while making pizzas, block the buses in Omaha, intercept Tucker Carlson’s mail delivery, AND hack? That woman surely is an inspiration. BREAKING: UPS Responds To Disappearance Of Tucker Carlson Package ‘Damning’ To Biden | The Daily WireIf I were the GOP, just to be on the safe side, I’d check out Trump’s Chinese checking account. However, to be fair, and I am, this isn't a hack; according to the report the WI state party never lost control of its money. What they didn’t do is conduct basic due diligence before paying invoices.Most likely, the party was just paying invoices willy nilly style from unverified sources into bank accounts which didn't match the vendors' names and nobody thought anything was amiss until $2.3 million was paid. So chalk this one up to sheer incompetence.To conclude: The money wasn’t “hacked” at all. The GOP just got swindled, duped by some savvy crooks, that’s all. They must be so jealous…

That would have been me.I was invited to a party by a new friend, and it was really last minute. I flew to the cupboard to grab something for the potluck, and the quickest thing was a marbled brownie mix. I am mostly vegetarian, and it’s difficult to find pre-packaged food that is vegetarian unless it’s a single-serve item. With no time to boil grains or soak beans, I pulled the mix out and heated up the oven.It required butter or oil. Well, I don’t have butter, and I don’t have plain vegetable oil, that’s not healthy. All I have is olive oil. Well, oil’s oil, I thought, and I poured out the required amount into a measuring cup.I brought the brownies to the party and placed them on the dessert table. Well, the table is being emptied, but despite the appealing yellow and brown marbled brownies, only one brownie is missing. No one is touching the brownies!Well, I’m embarrassed. I feel like everyone at the party knows I brought the brownies and it looks bad that the pile is not going down. I know, I know, but I really felt like that. So I decided to eat one to inspire others to do the same.I bit into it.It was vile.It tasted like motor oil. Well, I’ve never had motor oil, but if I had, this would have been a good approximation. I had to find a corner and spit it out.As the party went on, I would randomly go over, pick up a brownie, and toss it in the trash.Apparently olive oil is not a good choice for brownies.

I think it depends what kind of work you do, if it’s primarily single page apps with a Go API, or a more traditional web app. You may have slightly more verbose code setting up types etc, but you gain a ton productivity-wise from things like:incredibly rich and robust stdlibreally, it even has hex dumping!!a lot of things literally everyone needs are standard (good http client etc)better third-party package quality on averagestatic typing (obviously)less time reading package docs and due to toolingsimple package system (no need for manifests)simple & obvious public/private interfaces via lowercase and uppercasenormalized code, all Go code effectively looks the same regardless of authorless time wasted waiting for installing / deploying 250mb of node_modulesbuilt-in test framework (no need for something like Mocha etc)built-in benchmarkingbuilt-in templatingbetter error handling, explicit and forces you to consider fail pointsbetter stream implementation with io.Reader / io.Writer and friendscross-compiling makes for easy binary deploysless indirection for publishing code (no extra registry step)verbose but easy to read, no guessing, it’s very explicitless fragmentation (callbacks, promises, async/await, …)I personally find it much more productive, it may take a bit of getting used to – so I wouldn’t judge the productivity right off the bat, give it an honest try for a few projects.Go has fewer third party packages, but they’re generally much higher quality, and very normalized thanks to gofmt and testing being standard. You don’t have to deal with 150 test frameworks or a wide variety of coding styles (typically pretty unreadable in JS IMO).What you won’t find is something like Rails (at least that I’m aware of) for more traditional apps, but for single-page apps (what I typically work on) it’s fantastic.For work that goes “beyond” web apps, like event processing pipelines and so on, I would strongly recommend not using Node. IMO It’s very hard to produce a production-ready robust program in Node, as someone who used it for ~5 years.The one notable strength (could be considered a con as well) is the lack of thread synchronization in Node since it’s an event loop. In practice it’s not too difficult to write thread-safe Go (or “concurrency safe” as most Go people would prefer to say), however that is an additional layer to worry about. With that said, it also makes it trivial to scale your program to any number of cores.