HNHacker News
TopNewBestAskShowJobs

fargle

1,337 karma · joined August 28, 2019

submissionscomments
fargle··on Discussion on misuse of "open source" by dokploy closed without comment
the limited feedback from https://news.ycombinator.com/user?id=siumauricio here and the stonewall response to the, very serious, license issue discussion on github is very concerning.

this has every look of a potentially talented developer that seriously misunderstands the legalities and role of open-source. there's probably a way to do what they intend, but this ain't it. and you don't make "open-source" but say "mine! mine! you can't change it/use it".

does this violate any github policy? certainly the apache foundation should have a word.

fargle··on Discussion on misuse of "open source" by dokploy closed without comment
some discussion about the licensing situation from couple days ago: https://news.ycombinator.com/item?id=40195480

oh, and it was flagged. probably for self-promotion. of course.

fargle··on Ask HN: Choosing Between Two Jobs
> the other team members are the complete opposite and terrific to work alongside.

good!

> the defacto leader of our group/team (he has no actual managerial title or responsibilities) belittles or speaks over people all the time

> any ideas i have are either dismissed outright or pawned off later as someone else's.

not good.

as sibling comments have alluded to, you need to fix this issue in place. unless it's the real manager you have a hopeless beef with, it's not time to quit. oh, and i'd expect apathy or a weak response at first. that's pretty normal. welcome to life. /s the best strategy is to be right. is this guy your actual manager or not? (not) who was the decision responsibility/authority? (not technically him, right?) and so on. you tell the real manager all of this and that you would like to not have technical decisions dictated always from a peer. you would like an area to work that you have some modest authority over.

so you need to be assertive. if you don't, you'll just make 15% less and still have the same team member issue somewhere else with a different name.

fargle··on Kayaker's hours trapped under rapids – writes about out of body experiences
well... that is writing.
fargle··on Detroit Makes the Same Mistake on EVs It Did with Japan
https://archive.is/B7NcI

please, if you are going to post paywalled links that aren't readable to most people, take the time to post an archive link

fargle··on US set to impose 100% tariff on Chinese electric vehicle imports
if you post an interesting link, that nobody else can read, then someone else posts the archive link to fix that, it isn't a "kindness". it's cleanup for someone else.

should we never speak of it?

fargle··on US set to impose 100% tariff on Chinese electric vehicle imports
it's not an attack. i just find it rude to post a paywalled article. why not take two seconds to post an archive link if you really need to?

because someone else will do it for you? is that really a decent attitude?

fargle··on US set to impose 100% tariff on Chinese electric vehicle imports
https://archive.is/P91pA

please if you are going to post a paywalled article, have the decency to post an archive link

fargle··on Was the 401(k) a Mistake?
"Ghilarducci proposed replacing 401(k)s with “guaranteed retirement accounts,” a program that would combine mandatory individual and employer contributions with tax credits and that would guarantee at least a 3 percent annual return"

good god! 3%? shoot me. even if it's "inflation adjusted 3%".

the whole problem is this:

- 401(k)s suck if you can't trust the individual contributor to contribute. oh, and sometimes the market falls over and takes a nap for a decade or so ¯\_(ツ)_/¯ there's luck involved.

- private pensions suck if you can't trust the employer to invest wisely and not "raid the pension fund". ask an ex-Delta pilot about that one. they got zero.

- government retirement plans suck if you can't trust the bureaucracy to not "raid the pension fund". ask a social-"security" recipient about that one. my latest statement says i'll be getting what is the inflation adjusted equivalent to $36 a week if i can wait to 67. /s

there's no plan that magically helps low-income, at risk, seniors or doesn't lead to the richer, smarter, and more well-off benefiting more than the rest.

two of those three have no way out, no fix. one of those three at least has a hope of working if you are smart and disciplined enough to contribute and not "raid your own retirement fund"

fargle··on Attackers can decloak routing-based VPNs
if you are on a public wifi, particularly if you can control an evil dhcp server, there are sooo many other ways to attack someone's pc client and network. this is just another. it doesn't even seem that unexpected.
fargle··on Attackers can decloak routing-based VPNs
always the breathless sensationalized vulnerability headlines...

it's interesting, but of limited usefulness - the device has to accept responses from a dhcp server. if an attacker controls a dhcp server, he's either on the network already or has already had to do a lot worse than installing a couple static routes to get there.

it's not nothing - a compromised home gateway could use this technique to sneak into a corporate VPN via a users' laptop, but if you have a compromised home gateway, you have a lot of other problems that could lead to the same result.

fargle··on Vacation ruined, they apologized – with a heartfelt note written by ChatGPT
well, shoot. these kind of responses were always saccharine and formulaic. "we sincerely apologize for the inconvenience" and "we appreciate your patience" and "rest assured ..."

oh so very "from the heart". as long as it changes nothing material, of course.

with AI, they'll be no more helpful or more human. but at least they'll be faster and spelt correctly.

fargle··on Bollards: Why and What
agree, but it's not really sarcasm/irony. it's more derision/snobbery. this isn't about whether one agrees or disagrees with the author's "more bollards better" platform, but the entire framing is off-putting.
fargle··on Ansible is a Lisp?
that's beyond a real stretch - is XSLT a LISP then? simply using YAML (or json or any equivalent data/markup syntax as the basis for a DSL syntax does not make it homoiconic.

in this case, the very rigid structure of playbooks and tasks, etc. within YAML is also part of the syntax. just the fact that you can generate arbitrary YAML (or json or etc.) from within a copy utility does not come close to homoiconicity of a LISP. can you effortlessly move back/forth from data to code? is everything both code and data at the same time? what's the Ansible equivalent to quasi-quote, for instance? is a bash script that sources (or creates or evals) a list of variable assignments in bash syntax homoiconic? due to eval, bash would seem a hell of a lot closer.

and those really aren't "syntactic macros" either, unless you'd be happy to define an MS-DOS .bat file that generates and calls a .bat file fragment "syntactic macros". it's using an external file ffs.

Ansible is good for what it does, but it has an extremely limited and rigid "flow-control" (if we can even call it that) and is more of a declarative language/config file than a general language.

this represents a pretty naive superficial understanding of these LISP features.

points for making us think though.

fargle··on The world's loudest Lisp program to the rescue
wow! that is a great reference.

i've only found it summited a few times and only with comments here: https://news.ycombinator.com/item?id=10567360.

not a lot of comments and i suspect somewhat missing the point because this submission started with part 5, which intentionally is only part of the series exposing the pros/cons, limitations, etc. of various approaches.

fargle··on Resistance Against Git Merge Hell (2015)
the way i look at it is this: we actually use git for at least two different but related things

- a public change history (e.g. commit history of master, dev-1.0, whatever)

- a personal change history, especially useful when prototyping a fix or feature on some independent branch.

you might even call this independent branch "master" but it's your personal version of master in a clone on your laptop. it's a time machine, you can go backward/forward. you can make a change and then reverse course. you can commit every work-in-progress that compiles as you work get it running or passing tests. whatever you like. you can pull or merge or rebase as you wish.

when submitting it to the public "master" branch, you are effectively saying "i want to commit this package of changes on top of the master branch.

do you really want to see "fhgiry pulled from master into fix-splork-feature on date x" and https://xkcd.com/1597/ in your public history of master? every branch you merged from or rebased on and every failed attempt and spelling mistake and WIP and addressing of review comments?

or do we want to see a series of commits that just record the end result in a series of nice little patches that simply add a finished changes like: "splork: fix canoe paddle explosion issue by decreasing default gamma"

the common ubiquitous guidance to "never rewrite history" is nearly always valid for the public history.

converting a messy personal history into a neat series of patches/changes/commits that apply cleanly onto the latest public master should not fall under that same guidance. i'd say it's closer to "never rewrite public history"

fargle··on Pete Ballmer: what its like to grow up as Steve Ballmers son
mow the lawn! mow the lawn! mow the lawn!
fargle··on Google lays off its Python team
while i'm sympathetic, it still means you had a great deal going. if/when it ends you shouldn't get pissed off you got the opportunity in the first place - a visa isn't permanent.

to be clear - what i was reacting to was the author's idea that he should reject capitalism and/or start a trade union, after having been a very, very, lucky player of the capitalism game indeed. it pisses me off when people making N multiples of 6 figure incomes start forgetting how lucky they are and how much they personally benefited from that exact system. a laid off googler's worst day is many, many times better than the average guys daily life. in this country, let alone somewhere else.

fargle··on Google lays off its Python team
agree. i can tell it was a bad day for the author and it sucks. but it's irritating to sit there and blame the exact system and company that gave him the exceptional job and pay in the first place.

everyone who works in FAANG, if you are drawing an enormous salary and bonus, compared to the average guy, i hope you realize the how fortunate you are. i hope you are putting away, saving, investing, at least 1/3 or 1/2 of it. when and if this happens after a few years, unlike the average guy, you can simply choose to retire or take some time off and travel rather than the normal option of loosing your home and being completely ruined.

fargle··on California lawmakers rein in bill to limit car speeds
pretty much right. the traffic survey requirement only affects "posted" speed limits.

the unconditional "maximum speed" limit of 65 or 55 on two-lane [1] is not part of the speed-trap law.

the 55 MPH limit for vehicles towing (big trucks and cars and anything else towing) is a worthless relic and positively unsafe. there are only a few other states that do this, and several of them are busy repealing it.

[1] https://leginfo.legislature.ca.gov/faces/codes_displaySectio...

fargle··on Other People’s Problems
that's cute, and it is often true. but not "always".

sometimes when a group gets "wrapped around the axle" and the proposed thing is spiraling out of control (usually due to hallucinated requirements or group anxiety feeding on itself), "Just <simple option>" is EXACTLY what is needed, especially from a confident leader.

fargle··on [dead]
first of all, this is an obvious advertisement

it, itself, clearly constitutes spam in this forum

nobody wants to see this, "cold" (spam) email, "cold" spam websites.

nobody. you are a jerk who sells a product that doesn't work to businesses by lying to them that spam works and then you turn around and spam the rest of us. you wreck the internet worse than p0rn.

fargle··on Google fires 28 employees involved in sit-in protest over $1.2B Israel contract
sorry, but a peaceful sit-in in a public place or semi-public-place (shop, college etc.) is one thing.

in this case they were: - not-peaceful. damaging property. antagonizing people. - in a private space. in a private office in a private space. - in the employ of the very people they were protesting. OK, even if they had the right to be there (which they did not), the company still has the right (moral and legal), actually imperative, to fire them.

i don't agree that you need to "check your opinions at the door" at work. you can put up a poster or a flag. you can wear a t-shirt. within reason. you CANNOT harass your employer or other employees.

would you say the same: "it isn't necessarily just" [to be fired] if it were 24 KKK members protesting hiring H1Bs in otherwise exactly the same manner? if you can't, it isn't a protest, it's thuggery.

fargle··on Google fires 28 employees involved in sit-in protest over $1.2B Israel contract
it is a belief. it's a belief in actual freedom - one where we are free to decide whether to do business or not with who we choose. if we choose to contract with a FANG for lots and lots of money, but we have "sell our soul" and promise not to harangue the CEO in the mens' room, that's OK. if we choose not to promise that, for much less $$, that's also OK.

and checking your beliefs are the door is a strawman. you're allowed to have beliefs. you're even allowed to voice them, discuss them in a professional way. they do not have to be hidden. but you cannot harass/annoy/intimidate/etc. but if you still do not like those rules, that's fine too! don't sign up for them - leave.

if you were really principled in your beliefs, you would NOT "check them at the door" - you would not work there nor participate. but you can't have it both ways AND then claim moral high ground too.

fargle··on Google fires 28 employees involved in sit-in protest over $1.2B Israel contract
> What a soulless perspective.

disagree, strongly. you present a false dichotomy. you can be a human with a soul and disagree (strongly) with your employer and still take their salary to do your job. it's not your job to decide how the software you build is used - there's several democratic governments, shareholders, company officers, etc. that get to decide that. when you are an employee that is the deal you made when you decided to work for them.

> Most software jobs are not paying their workers a salary for them to become soulless robots. They are paying you to produce code, and to have expertise on the matters at hand.

agree. totally true. notice how they are specifically not paying you to protest global political issues in their executive offices.

> I will remain a free opinionated human, regardless of whether I am taking a paycheck or not, and if the company does not want a human, they can fire me and try to replace me with someone like you, or with an AI.

again, totally understandable and fine.

however, these people are not just "opinionated". they decided to stage a "protest". that is NOT what they were being paid to do. and they decided to protest their own employer. on that employer's property. you are free to have your own opinion about your employer, his politics, his customers, etc. you are not free to stage a takeover and make a public protest about it on his property. you are not free to disagree publicly and embarrass or harass him and then expect he will not hire someone else next week instead of you. if you don't like it: buy a majority position or run for office. if you really can't stomach it, then the only ethical thing to do is quit - you can demonstrate your conviction by sacrificing yourself. but you have no right to injure/annoy/bother anyone else about your political ideas at work.

from a pragmatic standpoint, that was stupid. from a practical standpoint, it will do nothing to help their cause, quite likely damage it instead. it doesn't demonstrate good ethics, "having a soul" or anything like that. it demonstrates incredible immaturity, entitlement, and naivete.

fargle··on 1800-2023 – IEEE Standard for SystemVerilog
zig: yes, it's very interesting. there's other parts i'm not sold about, but that idea is very interesting.

spinalHDL: yes, also interesting. although honestly, i really prefer SV. it's a shame that the language has become so complex, but a synthesizable subset still ends up being the best thing for me to efficiently describe hardware. what they did with generate() and parameterization (borrowed from VHDL?) is very nice. it's far, far, better than C++ templates for an analogous purposes. i very rarely need to use `if, `define in SV nowadays.

cpp: oh yes, i'm a nerd about languages/macros/meta-programming/etc.

fargle··on 1800-2023 – IEEE Standard for SystemVerilog
it would make me very happy if someday someone does a really comprehensive study of the places where specific techniques cannot be accomplished without a C/C++ style pre-processor. SV is very similar to C, but actually even less powerful. step #2, find a way to build a better macro/meta-coding system within the syntax of the language to eliminate the need for a textual pre-processor.

in SV, generate constructs are exactly this concept and have reduced the need for macros significantly, but we still can't quite get rid of them. but at least for me they are pretty rare.

fargle··on 1800-2023 – IEEE Standard for SystemVerilog
the differences from 2017 are relatively minor, so apparently that's not recent news? nobody told us tho. /s
fargle··on 1800-2023 – IEEE Standard for SystemVerilog
quick summary: not a huge change

one that is interesting is that they've improved `ifdef to allow boolean combinations. it was previously hard to accomplish what CPP can do with #if.

i wish there were change bars, but could not find a draft or a way to do a meaningful diff.

there's a paper by Dave Rich: https://dvcon-proceedings.org/wp-content/uploads/1114-Whats-...

fargle··on 1800-2023 – IEEE Standard for SystemVerilog
The 2023 version of the System Verilog standard has been released.

It's free via the IEEE "Get" program, which is awesome.

← PreviousPage 8 of 34Next →