cfv

Merge requests have been a gitlab feature since forever though. Like issues, and webhooks

Without even delving on the perverse sanctions part, it should never be forgotten that the whole point of git is that it's a distributed source control system. Grab your source and move it elsewhere. Heck, even an old forked gitlab community instance should work.

Github is good for the exposure, but it's their house, and so their rules apply, not ours. Don't rely on them to always be OK with you staying.

I want to like this article because I agree with the overarching general statement that the ActiveRecord pattern is troublesome.

But it's... not very good. He constructed his own interface in order to complain about it, an interface which is so subptimal that it lets him complain about how bad it is as if the pattern was somehow to blame.

In most Active Record implementations I've seen, a Record is a live tuple ("Active" "Record") and you typically have some form of Repository ("Books" maybe in this example?) alongside of it which is responsible for carefully and optimally building the record objects.

The pattern itself says nothing about how to query things, it talks about a kind of DAO that has convenience methods to access and manipulate a tuple.

Also, what's with the REST rant? I don't think I understand how that's linked.

Yarn's new version does a bunch of weird, complex to reason about stuff that's closer to a bundler than it is to a module manager: https://github.com/yarnpkg/yarn/issues/6953

Microsoft does have a much better track record in terms of keeping their products alive than other Way Way Large companies that could have made this acquisition, and for that I'm pretty glad.

That said, and just in case their notoriously warlike legal team manages to fumble this somehow, I'd like to take the opportunity to remind every other frontender that Verdaccio (https://verdaccio.org/) exists, is easy to implement, and relatively low maintenance.

The concrete thing I can't find anywhere is the actual, on-paper set of rules this people set up, ideally grafted to some kind of explanation on why this ruleset made any sense in context.

Speaking in the most general sense possible, having your armed forces firmly under control is traditionally a core part of staying in power; it's also very generally true that no person making the rules is going to actively hinder their own ability to keep doing so.

That's why it's super important to keep them aware that the little people are watching and taking notes; that's literally the only trump card we all have.

Look, I'm asking for an actual memo here, I'm not interested in playing whatever game you seem to want to play.

Can you help me find this thing please?

From this point forward: https://www.google.com/amp/s/www.nytimes.com/2019/04/24/us/p... the DOJ has allowed the WH to refuse to comply with a bunch of subpoenas, and there's no amount of partisan rhetoric that can hide that fact. It's simply not up for debate, sorry.

That said, I don't know what are they standing on to be able to do that without any court just sending them all to jail.

Congress was explicitly told they could not do this by the DOJ, but news weren't clear on the legal reasoning, relaying instead the handwavy explanation by Barr on the popelike infallibility of the president's office.

I'm really curious about the actual legal reasoning behind this, it's got to be a fascinating read.

What's the legal reasoning (if there's any) to keep her locked up and ruin her financially while not being able to swing the same punishment at all those people who refused to testify in the recent impeachment?

There's stuff like Capacitor with which you can build decently native-feeling PWAs that can be bundled into appstore-ready trinkets if you so desire. I'm a huge fan of the insta-deploy feature PWAs offer tho and routinely lobby for them at my company.

Clients seem to prefer apps for some reason tho.

First things first, thank you very much for the fast response!

It's very true that all the prepwork is pretty costly, hence my eagerness to try and adopt random bits and pieces even at this stage; it might end up saving us time down the line haha

While I have you around... what would be a good toy to build with this? Our megalithic, business rules heavy app sounds like a potential good fit for the Redwood, but it's entirely too large a bite to tease our engineering leads with.

While this looks great I'm having trouble fitting it to any of the projects I'm already working on.

We already have all those pieces in place, along with the ability of swapping any one piece with a different one; say, if we wanted to go RESTful we only need to swap one block.

It does look gorgeous tho; how would one go about gradually adopting it?

ESR clearly blew a gasket and banning him, however temporarily, is a necessary thing.

He does, however, make a couple goodish points:

- Zero tolerance CoCs are a disgrace for software because the friendly-or-else atmosphere they help create makes horrible-but-personable people thrive in places where they'd otherwise be laughed out of the room. Politicians excel at this game; see Congress' CoC forcing reps to call each other "my good friend" instead of (for example) "this baby murderer over here" no matter how horrible a proposal they made is.

This is a Hard Problem to solve though.

- The ESD is a terrible, unusable license that shouldn't be called Open Source, for various reasons like how its "freedom" functionally depends on how litigious the creators of a software piece woke up that day waaay more than traditional OS licenses, giving authors a direct link between their personal values and their actual, inanimate work product.

Imagine being able to buy a yoga book, then getting sued because the author required you to be a vegan first.

Give ESR a couple days rest, knock on his door and have a proper chat? Maybe this can actually be resolved with actual honesty for one.

As long as they stop leaving apps dead on the water whenever they decide to maybe develop something remotely related, as has happened several times in the past, then I guess this is good? My previous exp with them isn't super encouraging unfortunately.

As the author states, encrypting your data impedes scanning it, so any encryption that is actually worth anything inmediately puts them at fault, so it wont be applied.

Any unmonitored user upload is at risk here.

This is dark.

When the game is at this stage it's better to just not play.

When an advertising platform has to pay fartsniffers to follow you around to offer marginally better ctr than email spam, maybe just don't run ads?

Work manually on growing networks of users, actually walk up to them and chat, talk in relevant business forums and you won't spend thousands of dollars you don't have casting a net in hopes of finding people who more likely than not just don't want to be associated with your practices.

This is an actual HTML tag, not a github thing

https://jsbin.com/timafew/edit?html,output

Not OP, but we've used Ant design and the gov.uk systems with good reception from our clients and only minor hiccups with end user testing

On paper, this sounds absolutely awesome and a huge game changer.

I'm super concerned about the military applications tho. Giving functionally endless, mostly free power to warmonger countries with the ability to field drones is something extremely concerning for me.

How would this compare to brotli-ed svg?

My biggest issue with MVC is that in my experience it always ends up having the C being glue between fat Ms and fat Vs, with multiple views ocasionally growing tendrils between one another.

As in, not the pattern, but the real-world usage of it. Development constraints always end up corrupting the pretty pattern in ways that make the current problem at hand easier to solve, and this de facto architecture IMO never ends up looking like proper MVC for me.

I want to say I like Action-Domain-Responder better, but I haven't seen any real-world implementations of a ROA with it yet.

CQRS comes to mind. spam events from user interaction, respond to them with any number of disjoint event handlers, with a tiny core runtime that ultimately acts on a specific subset of those events destined to modify the DOM in some way or another

This is nuts.

a) They are charged with conspiring with each other to this, but simultaneously b) "fits a disturbing and unacceptable pattern of state-sponsored computer intrusions", and in the process they managed to commit c) "conspiracy to commit wire fraud"

None of those 3 things make any sense in the face of the others. How is doing this kind of things even legal?

> Formed in 1946, it is a cooperative brand managed by a cooperative body, the Gujarat Co-operative Milk Marketing Federation Ltd. (GCMMF), which today is jointly owned by 3.6 million milk producers in Gujarat.[4]

I mean, kind of? idk if India has the concept of a worker's cooperative company but this is not super far away from it

CSS layout is, in more than one way, like string semantics in c++. A whole lot of innovation and a few gross missteps happened there, with the side effect of pushing everyone and also the language itself forward

Literally the same thing can be said about any language that is not niche tho.

Also, wee nitpick of mine; you don't have to build any state on your own, the interpreter does that for you as one of the core principles of the system.

The guy has absolutely 0 obligation towards anyone. There was 0 money exchanged, there were 0 contracts signed, he's free to take his ball home.

Hope the people who caused this are happy now.

Is it still possible to unpack the asar, rewrite the source, and repackage the asar?