skysight-inc/HackerNews huggingface dataset:
Everyone who has done MVC long enough would also know that the controller is the very thin layer where services are injected and models are passes to.

The controller should have and only have logic which absolutely cannot be moved to a service layer.

Too many developers use controllers as part of their logic layer, instead of simply using it as a router for where models should be directed on a service level.
Reading the issue laying out the reason for taking this step, it all seems quite reasonable and mature: https://github.com/request/request/issues/3142

TL;DR: at over a decade old it's a primordial Node lib which has become increasingly difficult to evolve as the platform introduces new features, so rather than break every user with a massively disruptive new version that embraces modern features it's going to attempt to quietly sunset to free up the oxygen in the room so that new libs can grow.
I think what GP is saying is that what people call "Waterfall" is not what Waterfall was originally defined as. https://en.wikipedia.org/wiki/Waterfall_model#History
I wouldn't work for a corporation that organized "militant, corporate-backed political parties" either.
Japan does real estate development with banks and loans like the US does, and interest rates are even lower so it's easier to borrow a large sum of money. Can you explain what you meant about the finance industry not allowing prices to appreciate?

Their zoning is where they have obvious huge differences. The zoning categories are set at a national level and limit how restrictive local cities can be (there's 12 categories based on nuisance level). The higher zoning usually allows lower density also, so cities just start with a little extra zoning headroom that allows them to grow over time. They also automatically permit things that follow zoning. [1]

In the US zoning is more local, often there are many more zone types that are much more restrictive about what they allow (it's more micromanaged and often prohibits things like mixed-use in addition to multi family). In many of the biggest markets even projects that follow zoning are usually not allowed, every project is an individual years long fight. Also in cities like Los Angeles the zoned-for capacity has actually dramatically decreased over time, even as the population grew. [2]

Some of these policies may be a legacy of people deliberately not wanting it to be too affordable, because neighborhoods didn't want low-income people to move in. Of course now in many places even middle-income people can't afford it.

I think, from a social justice perspective, the US policy has been an abject failure. It's increased pollution (from long commutes) and homelessness. It's deprived people of good paying jobs, since they can't afford to move to the locations where they're available. It's squeezed the middle class and enriched landlords, there's even debate that housing may be the most important contributor to wealth inequality. It's anti-environment since higher density has less environmental impact on a per-capita basis. I'm sure there's some upsides, but I can't see any that remotely justify the long-term costs that these policies have brought about.

[1] https://marketurbanism.com/2019/03/19/why-is-japanese-zoning...

[2] https://www.salon.com/test/2015/04/05/the_incredible_shrinki..., graph at: https://www.austincontrarian.com/.a/6a00d8341d04dc53ef01b8d2...
Latinendian vs. Arabendian
It might behoove you to read a bit more about the well-documented nature of employment discrimination in the tech industry. Women are systematically underpaid and denied raises and promotions compared to men, which tends to make their cases weaker when going to a new company as well.
> This document is a collection of Unix/Linux/BSD commands and tasks which are useful for IT work or for advanced users. This is a practical guide with concise explanations, however the reader is supposed to know what s/he is doing.

Something I bookmarked back in June 2010 :-)
See https://news.ycombinator.com/item?id=22357897 .
Associating negative traits with men is exactly the point. The basic notion seems to be that men are “privileged oppressors” and women are “oppressed”, which fundamentally means that even if a woman engages in the exact same behavior, it somehow doesn’t count because women are collectively the victims in all of this anyway.
My cousin's boyfriend's sister went up to the waterfall, and when they found her body 12 months later--after delivery phase--she had been completely burned out from the inside. And there was this thing... that nobody wanted, that didn't work right, just sitting there next to her. Nobody wanted to touch it. So some guys from the federal government came and picked it up with tongs, and said they'd put it in the Source Control Repository facility out in New Mexico, so it couldn't hurt anybody else.
> One has no incentive to excel, as promotions are based on years "served"

I really dislike any kind of system that more tightly couples people's well-being to their employer. Government regulations on industries like safe working conditions can be great and really help to protect people. No matter what company you work at, they'll protect you. But a company union, where I am only protected as long as I work in this one place, just isn't appealing to me. If I get transfered to a bad manager, or any number of other things happens that makes the job a little worse, now I have to worry about leaving the union, maybe throwing away the number of years I've been working towards my next promotion, etc. Similarly, I really dislike employee healthcare plans for being a huge hurdle to anyone who wants to leave a job and work for themselves, or work part-time to spend more time with their kids, or take on any number of other flexible work options.

I don't buy that the only possible choices are either to have no protections and continue to erode the middle-class standard of living, or force everyone to work 40-hours a week full-time at a big corporation the rest of their lives to have decent conditions. I really hope other alternatives like UBI start to catch on more.
I can't get too worked up that there are some bad electricians (and I'm imagining that this is true for any field) who are also union members.

My brother in law's a solo residential electrician who occasionally does a little commercial work. Been doing this for 20+ years. He works hard to keep up with codes, always spends the time on the job to do the work to good standards, etc. His observation is probably 80% of the homes he's come into, whether done by the homeowner or by a previous electrician, the work is shoddy to the point of being dangerous.

I'm honestly not at all surprised if there are bad union electricians, it seems like there are a LOT of bad electricians out there.

Sucks that they're rotating through the union hiring pool, though. I'm sure that was super frustrating.
And why would it not be?

If I don't like my job, I get another one. It's easier to do this as a software engineer than almost anything else.
First, most people misunderstand democracy. Democracy is that people have a say over in proportion to how much a decision affects them. Command-control hierarchies don't have this property. I like to call democracy 'distributed' decision making vs centralized like command-control.

Have you read studies that command-control hierarchies make better decisions?
Will they publish the union agreement? Wow... we will go from job/salary comparison sites to sites comparing transparent union agreements.... That is a step up!
You can only unionise if you struggle?
My comment is too old to edit. I tend to listen to Lex's more but I thought this spectrogram comparing 8 seconds of Lex v 8 seconds of Sean is hilarious:

https://imgur.com/a/jo4eNWK

Pretty easy to figure out who's who. Sorry buddy, haha.
Watched the video. Nice job with following through.
I like this a lot, not as an alternative to MVC but as a kind of conceptual refactoring of the same ideas behind good MVC implementations that's very easy to explain and doesn't have as much ambiguity.

I've posted a version of this comment before, but my main problem with MVC isn't that it's a bad architecture, just that in practice there's a huge amount of disagreement about what MVC (or MV* more generally) actually _is_, which can lead to confusion or weird/bad hybrid implementations.

I tend to use the "model" and "view" concepts a lot when discussing architecture, but in my experience it's almost always a mistake to try and reference any specific MV* pattern for explanatory purposes - it does not have the effect of making the discussion clearer.

The issue is that there isn't actually a consensus about what constitutes the definitional features of these patterns, especially when it comes to how the concepts involved actually translate into code. For any sufficiently notable discussion of an MV* pattern, you're going to find an argument in the comments about whether the author actually understands the pattern or is talking about something else, and typically the commenters will be talking past one another.

Note that I'm NOT claiming that there's anything wrong with MV* as an architecture, or your favorite explanation of MV* - it may be perfectly well defined and concrete and useful once you understand it. The issue is a feature of the community: lots of other people have a different (and possibly worse) understanding of what MV* means, so when you start talking about it and your understandings don't align, confusion arises. Getting those understandings back in alignment is more trouble than the acronyms are worth.

I've seen enough conversations about concrete development issues suddenly turn into disagreements about the meaning of words to realize that nothing useful is conveyed by mentioning MV* and assuming anyone knows what you're talking about - it's better to spell out exactly what you mean in reference to the code you're actually talking about, even if you have to use more words.

I like this MOVE scheme because it seems to me to divide up the conceptual space at the joints in a way that's relatively hard to misunderstand, and it seems a little easier to see how to directly relate those division back to code.
> MVC is a phenomenal idea. You have models, which are nice self-contained bits of state, views which are nice self-contained bits of UI, and controllers which are nice self-contained bits of … What?

The implication is that what goes into controllers is not well-defined. But if what goes into models and views is well-defined, as the author agrees, then defining what goes into controllers as everything else is actually a precise definition.
I too love the best tool for the job, which is why blanket statements saying session IDs should always be used for authentication are very puzzling to me.

HTTPS, HMAC and asymmetric keys are battle tested and proven to work as well, that was one major point of the article.
That's because OP needed a clickbait title.
I don’t think that will ever happen. The knowledge to develop the tools is too specialized and the user base too small. The same goes for any RF tools.
What's with the anecdotes on this thread? The OP was trying to make substantive statements about unions in general and why anecdotes are ineffective in describing them, and your counter was to provide yet another anecdote?
Also, "mp3 is license free" rhymes :)
Unions, in my experience, exist to help keep mediocre, unmotivated employees employed.

What's wrong with "mediocre" employees staying employed?
I would love to understand the dynamic better, so please correct me here or chime in.

Tech is has one of the best combinations of (lucrative + meritocratic) I've seen. Fields that pay similarly or better (law, medicine, investment banking) require either significant time-consuming credentials or significant time investment as an underlying (like IB analyst).

The interview process does require intensive preparation to land a top spot. However, your compensation package increases proportionately to the preparatory time. From the mind of a top performer, wouldn't you want to seek out the best of the best, rather than settling for median wage? It seems like unionizing will encourage the top workers to leave while the below-average to stay, dragging down the overall talent pool.
What an awful decision by those employees. They’re in for a rude awakening.
That will kill your company way, way faster than any union will.
Putting aside that if "I may get slightly less rich but still never have to do anything, whatsoever, that I don't want to, ever, and neither will the next two generations of my family" is the risk please fucking sign me up for taking that "consequence of failure", I don't even need the chance at up-side.
From my understanding of the certificate transparency program does not mitigate the threat of them simply not disclosing a certificate they signed. Ultimately this still gives them MitM capabilities as long as they control the traffic or am I mistaken?
I guess they didn't think they could win their vote when there were ~110 employees but they did when there were 86.

I guess things were so tense between the two camps that many people moved on.
> Fallthrough allows you to run partially the same code for different inputs.

True, but it's a screwy way to manage such overlaps. The volume of errors and confusion exceeds the benefits in my opinion. There are other ways to do such. For non-trivial conditionals (such as overlaps), if-else is often the better tool anyhow. Case/Switch should only be used for simple mutually-exclusive value look-ups.
Writing advice: Show, don’t tell: or should you?
It puzzles me why he never became a citizen. He moved to the UK in 1966, that's 54 years now, and it was even before they joined the EEC sometime in the 1970s.
It's worse than that. MVC is not only not dead, this little essay has conveniently reinvented it! (The C became an O, and the E was always there in some form.)
I've only skimmed the code but it seems to me that the repo is an art piece just as much or more than it is a software project. The medium is code but that doesn't mean that it needs to adhere to professional standards anymore than someone's woodworking project needs to adhere to building codes.
Most people do waterfall still. They don’t know how to think in any other way.
It’s an advert to watch the program.
Ring, Nest normalize American surveillance, turned us into a nation of voyeurs
What's your basis for that statement? Japanese social norms are quite communitarian, especially around contagious diseases.
> We've built and shipped 7 products recently and if there's one thing we've learned, it's that your personal relationship with your customer is your secret weapon as a startup. Having customers email support@company.com or message a bot via Intercom doesn't feel personal.

Agree with the personal relationship with the customer part. But if the email is <realname>@company.com, wouldn’t that be personal? I do see giving a phone number as way more involved with the customer.

> From a customer’s perspective, they’re just texting a single number. They’re not frustrated with messy tickets or being routed to 3 different people.

Isn’t that what happens here in the backend — some messy ticketing system in Slack (which I gather isn’t a ticketing system) and several people handling responses for the same customer/issue and a potential lack of coherence in responses?

I don’t mean to pick on you. I really see value in providing a phone number to customers and telling them they can text or call anytime. But somewhere your marketing message seems a bit off to me, and doesn’t make sense on the points you’re railing against.

All the best!
"For some strange reason when a bank calls the FBI things move with a high level of expediency."

Except when these hackers are in China, etc...
Don't blacklist, use shorter lived tokens and have the client refresh as needed. A 10-15m token is plenty long life and not so long as it's a huge risk window, more than even a shorter window,.
You don't get to decide who leaves. If people don't like a companies dictator then they are free to go join another company. It's this competition in the free market for labor that helps prevent the abuses of tyranny.
Does anyone here have any experience with JuJu? From how its marketed, it may alleviate much of the burden of setting up infrastructure (especially if using charms provided by the charm store).
Sorry, so you're saying that Detroit's auto industry went away because they unionized? The thing they did many decades before that?
Kickstarter has had no intention of going public and doesn't issue shares like that to employees at all.
The whole thing started as political stunt sort of due to the neo-nazis' outcry over some anti-fascist project. It was a mess (of course not sympathizing with Breitbart at all for the record).

And now they just added a whole new overhead of dealing with their initiative. Look at that one-pager of extremely poorly formulated demands. Obviously the company will have to spend resources sorting this out, through lawyers, through hiring MORE managers to deal with these managers. KS is NOT a bad place to work at by large margin it's a GOOD place to work at.

I am hearing already around here in NYC that no I don't want to go work there next to these folks, I am a developer not a polit-sci wannabe etc.

The spectacular outcome would be if KS fails to raise more funds because of this which is quite a possibility.
Kickstarter prints money, so I don't think they'll be hurt too much by this.

I think that Kickstarter as a company could exist in its current form with little change for a long time. I wonder how the culture works around there.
Please solve it then. Start with AT&T's union. I await your results.
Yeah, this "we can't extend password beyond 8 characters because legacy systems" argument does not hold water.

My experience: built a Web site/app for: a) major bank b) major corp, back in the days when Web presence was kind of a new thing. ~15-20 years ago.

You build a new (Web) app and treat the legacy system (happened to be some mainframe) as a backend or whatever. Add new tables to hold user's credentials, email addresses, and whatever else. Link the "new" credentials with the old "account id on mainframe" or whatever. Not really rocket science.

BTW - there was no such thing as an "old password table with max 8 character", not for retail customers. Retail customer did not have a password, or email.
Controller = Operations + Events

Ben Jaffe of Udacity cally is MVO where O = Octopus.
Basically, as the author points out, Models and Views are relatively well defined, but the Controller can be anything. Octopus, ViewModel, or in this case Operations and Events.

I do think Operations and Events are clear, but

1. are they comprehensive and

2. do they organize the code more intuitively?

It seems like you would want to put them in the same place since Events will trigger operations that operate on the model and the view. Sort of like a controller... oh, wait.
As have monarchies and dictatorships. So where does that leave us? The conclusions that all forms of government make horrifying decisions?
It is "proven", not in a mathematical sense, nor a scientific sense, nor an engineering sense or even a legal sense. It is proven in a javascript sense.
What a great analysis and reveal. Thank you!
> No new changes are expected land. In fact, none have landed for some time.

That's not what "deprecated" means. That's "maintenance mode".

Deprecated means no new clients should use it, and existing clients should migrate to library X or Y, because it's going to be deleted by 202X.
https://youtu.be/WgcjvcKHZKE

See how the YouTuber put Hindi in the title of that video? That's what I'm talking about
It appears to be spreading in the community now, which makes me think stopping a pandemic at this point will be very hard. One can only wonder what happens when it reaches places with much weaker health infrastructure, such as Africa and also many parts of India.

This seems to me like an accurate assessment of the situation: https://news.harvard.edu/gazette/story/2020/02/harvard-exper...
Maximizing Code Reuse in React
Seattle had a problem with Lime Cars.

People would put their Lime Car on a ferry and head west. As soon as the car lost reception from its range of allowance, it essentially was bricked. The car would have to wait for the ferry to come back to Seattle and be towed off.

This was shared by a friend over Labor Day.
TempleOS Source Code on GitHub
Cheers!

> And I hope it is clear that I'm not trying to attack you, but trying to express a different view point (and a particular frustration I experience being a scientist).

Yes, it's clear. :-)
I still don’t understand the value in this. How is this different from Apple Facebook Zendesk et al. contact platforms which provide certain level of anonymity to the customer ? Also is this a matter of simple Twilio to Slack hook integration ?
Depends.

The whole entertainment industry is unionized in L.A.

I know an actor from Las Vegas who moved to L.A. and got a role in a TV commercial and was surprised to see somebody else standing in front of the cameras and was surprised to find that every actor has a "stand-in" who is there so they can set up the equipment, then the real actor is fresh when he does his scene.

These costs add up, but there are many specialists who are highly productive. For instance, setting up and tearing down sets is a special form of carpentry which the average carpenter would take a change of mindset.

Union labor helps maintain a productive and talented workforce that gives L.A. a comparative advantage. Being at times the the documentarian who travels light and feels it is extravagant to have a sidekick that sets up lights it heavyweight but it maintains a world-beating quality standard.
That is right. And having service layer which dictates model changes, db ops and with its result a view change is pretty close here. This move pattern also reflects a bit the reflux idea of events and actions on models (with my limited redux knowledge).
Important caveat: BigDecimal is arbitrary-precision, not infinite-precision. Using it still requires you to think about the precision of each number you operate on.
Can you elaborate how Kickstarter is now ruined? As a creator and backer, this makes Kickstarter better for me. The organization as a whole is maddeningly unresponsive to me, but the workers who voted for, and organized, the union have been my strongest advocates.
For larger teams that aren't startups, we don't intend for this to be used for everyone. We think it should be reserved for your most important customers. In a lot of B2B businesses, a handful of customers account for the lion's share of your revenue. You want to build a personal relationship with them and make sure they are taken care of and happy. We think it's best to stratify support and give your most valuable customers direct access to your core team vs general support where they can get lost. It's worked well for us (we have 10s of customers) and we think it can work for just "VIP" customers at larger companies
Since React got hooks it could be interpreted as MOVE.

Components being Views

And

Hooks being Operations
> A one-pass compiler for a subset of C, relying on a recursive-descent parser, doing the lexing, parsing and code generation in lockstep. The generated code, consisting of abstract machine instructions, is then executed by an instruction fetch and execute loop.

This should be added to the README.
Is that with spectre/meltdown/etc protection on?
I'm curious, why do you refuse to install node on your computer?