Careful, you have to also add --no-preserve-root to make sure you get all of it out. If you leave the roots, it'll just grow back later!
(But seriously, don't actually do this unless you're prepared to lose data and potentially even brick your computer. Don't even try it on a VM or a computer you're planning to wipe anyway, because if something is mounted that you don't expect, you'll wipe that too. On older Linux kernels, EFI variables were mounted as writable, so running rm -rf /could actually brick your computer. This shouldn't still be the case, but I wouldn't test it, myself.)
Fun fact, rm -rf /* does not need --no-preserve-root. It will happily start as technically, according to the preserve root check, /* is not root as the target is not /
It’s slightly different. Your shell will see the /* and replace it with all the directories under /, e.g. /bin /dev /etc /home etc. So the actual command that runs is rm -rf /bin /dev /etc /home etc.
Static, low-js, HTML tags used-as-intended, some basic CSS for formatting, responsivity and dark/light. Modern-looking accessible webpage from scratch done in half a day.
If we assume “half a day” is 4 hours, and 500 pounds. That’s 125 pounds per hour. Which isn’t the worst rate. Assuming it’s actually capped at 4 hours and we all know that if it’s your dad’s friend, this is not going to be a set and forget kind of thing. So that 4 hours quickly becomes 10. And suddenly you’re down to 50 pounds per hour. And then if it’s actually static and simple and good, you still have high odds of getting insane feedback demanding changes to make it worse. A motherfucking website would actually be the best option, but wouldn’t get you paid. At that point youre just doing it for the lols.
But ultimately, this isn’t even about the rate or how much time this will take. this whole scenario depends heavily on the son here. Is the son unemployed and living in dad’s basement for free? Then yeah. Sorry, he should probably take any work he can get for any rate he can get. His dad gets a lot more say in how things work financially if the son is relying on him financially. But if the son is already working a full time job and living in his own house? Then no, I don’t care what the rate is. Don’t commandeer other people’s time. Don’t make deals that people haven’t agreed to. Come to me with opportunities, not demands.
You’re not wrong, but a lot of time those webpages aren’t overengineered because the developer wanted it to be, but because the client kept making more and more demands.
The irony of some dude trying to prove a point that a website doesn’t need to be bloated and burdened with all the design and fancy scripts, just for other people to incrementally built on top of that idea, one-upping each other in the process, mimicking the exact evolution of the modern bloated website as we know it.
Honestly I hate the fact that browsers’ default CSS exists. The person doing the frontend should have to specify their “default” CSS before the website even loads. I say this as both a user and a programmer, the same website shouldn’t look different or break on different browsers unintentionally due to the browser’s CSS, and I as a developer shouldn’t have to rely on reset sheets to try to patch that.
Everything would be better if it were swapped around, instead of picking out a reset sheet for a site you pick out a default style…
The world would also be better if browsers rendered pugjs/slim and scss/sass and those were the default rather than html and css but I digress…
Yeah I think that’s what he meant. You don’t want CI editing commits.
I use pre-commit for this. It’s pretty decent. The major flaws I’ve found with it:
Each linter has to be in its own repo (for most linter types). So it’s not really usable for project-specific lints.
Doesn’t really work with e.g. pyright or pylint unless you use no third party dependencies because you need a venv set up with your dependencies installed and pre-commit (fairly reasonably) doesn’t take care of that.
Overall it’s good, with some flaws, but there’s nothing better available so you should definitely use it.
I’ve used pre-commit pretty extensively over the years and I’m confused.
Each linter has to be in its own repo (for most linter types). So it’s not really usable for project-specific lints.
Not sure what you mean by this. I have pre-commit set up to do linting in several different projects, and even have it running multiple differently-configured lint jobs in the same repo.
Doesn’t really work with e.g. pyright or pylint unless you use no third party dependencies because you need a venv set up with your dependencies installed and pre-commit (fairly reasonably) doesn’t take care of that.
Again, I have pre-commit set up on multiple repos running pylint with multiple different plugins. Pre-commit absolutely does take care of setting up venvs with needed dependencies.
Not sure what you mean by this. I have pre-commit set up to do linting in several different projects, and even have it running multiple differently-configured lint jobs in the same repo.
I don’t mean using lints, I mean writing custom ones. Say you have a custom lint you want to use but it only will ever be used for that specific project. You can’t just put the lint code in a subdirectory. It has to go in a separate repo.
Pre-commit absolutely does take care of setting up venvs with needed dependencies.
Again I think you might be misunderstanding. It will install pylint fine, but if your project does e.g. import yaml, it’s not going to set up a venv and install pyyaml for you.
Say you have a custom lint you want to use but it only will ever be used for that specific project. You can’t just put the lint code in a subdirectory. It has to go in a separate repo.
You can run locally defined hooks with pre-commit, just define them in the repo: local section of the .pre-commit-config.yaml, and have it run a bash/python/whatever script or something that invokes your custom linting, wherever it lives in your file structure.
It will install pylint fine, but if your project does e.g. import yaml, it’s not going to set up a venv and install pyyaml for you.
Yeah I misspoke there. For Python based stuff, it uses the currently active virtualenv or your global python install, so it relies on you installing your own dependencies. Which isn’t really that big a deal imo, because you need to install those dependencies to run/debug/test locally anyways.
You can run locally defined hooks with pre-commit, just define them in the repo: local section of the .pre-commit-config.yaml
Sounds like you’re just googling it rather than actually speaking from experience. Suppose I have written a Python lint and it’s in my ci/lints/foo folder. How do I tell pre-commit that? (Hint: you can’t)
Which isn’t really that big a deal imo
For small Python projects, maybe not. The project I’m working on has multiple sub-projects and those each have their own venvs, pyproject.tomls, etc.
Sounds like you’re just googling it rather than actually speaking from experience.
Like I said, I’ve used pre-commit for multiple years now. If you can run your lints from a command line, you can configure pre-commit to run them.
The project I’m working on has multiple sub-projects and those each have their own venvs, pyproject.tomls, etc.
Monorepos definitely make things a bit trickier, but again, you absolutely can write a local pre-commit hook that runs a bash command or script that 1.) activates the necessary venv and 2.) runs the lint command. I know this because I’ve done it, multiple times.
If you can run your lints from a command line, you can configure pre-commit to run them.
Yes but the whole point of pre-commit is it takes care of installing the lints. For most supported languages this requires the lint to be in its own repo. That is very annoying for project-specific lints that you would ideally want to just put in a subdirectory. Does that make sense?
can write a local pre-commit hook that runs a bash command or script that 1.) activates the necessary venv and 2.) runs the lint command. I know this because I’ve done it, multiple times.
Yeah there’s not really any point using pre-commit at that point.
Pre-commit hooks is a common approach to this, so that whatever is committed gets processed. Another possibility would be to set a bot on the repo to do automated commits after human-made ones, but that can get a little noisy.
Tabs are objectively the better choice as it allows each dev individually to decide tab width in their editors. Spaces in contrast don’t allow this same flexibility as they are used for much more than simply indentation, for example you likely put a space after each argument or operator IE func(arg1, arg2) or 1 + 2.
Sometimes. I love auto formatting, I spam the shit out of it more than I spam save but it’s definitely not perfect. It gets real confused with inconsistent indention like that. Especially with Python it’ll fuckup
Code can be viewed in more than just an editor. It might be in a terminal, rendered in a browser, etc. Sometimes you might even have to view it in an environment you don’t control. I am very disinterested in configuring each and every tool to have sensible tabstops, if such a tool can even be configured.
Then don’t? The whole reason nearly all the spaces guys do 4 spaces is cause that’s the nearly universal tab width. You won’t like this but the same exact argument can be made for spaces yet I’d bet you haven’t even once configured the width of those.
I don’t actually change tab width, it’s the default 4 spaces equivalent for me but just because I don’t take advantage of the ability doesn’t mean I should prevent others from doing so.
What’s yaml have to do with anything? It’s like python with syntactic whitespace which is unrelated to this discussion. The Tab vs Space debate is entirely around non syntactic whitespace which doesn’t effect how the code is parsed. And yes Python technically does both tabs and spaces but it’s all sorts of fucky.
Terminal editors while still used a ton aren’t really what I was referring to. Newer terminal editors such as Helix have tab width configured per language most of which default to a width of 4 spaces but toml/yaml both default to 2 spaces. I was mainly referring to GUI editors as frankly that’s just what most people use nowadays. JetBrains IDEs, Visual Studio, Eclipse, VS Code, Notepad++ were primarily what I was thinking of as I’ve used all of them and they all default to a tab width of 4 hence why I said nearly universal. Also I said nearly terminal editors being the only editors I’ve used that don’t default to a width of 4 seems like a fair usage of the term.
This is simply false, many systems have them configured by default to 8, particularly most CLI tools. Git, for example, is 8, and btw, changing it is not readily done and requires you to hack around it by using a custom pager command. In fact, all core gnu utils (and even bash itself) default to 8, as well vim, emacs, nano, gedit, etc.
I use 2 spaces since I work in Haskell, which is a significant whitespace language where you want certain syntactic constructs to exist at a different level of indentation from your main code block. So yes, I have configured it. 2 spaces is also exceedingly common for HTML (browser Dev tools renders HTML with 2 spaces, even).
There is not a universal indentation width, though it is almost always universal within a particular language or perhaps project, in which case it’s much better to have everything standardized. Code formatters enforced on a project are the norm, and those are way more impactful on how the code is read. But they are valuable because consistency is valuable. And yet, somehow you don’t have huge scores of developers complaining about being forced to format their code in a way they don’t like.
As I said, you don’t necessarily control the environment in which you are viewing code. A common example is reading code over a shared screen. So you can easily end up reading code in a way you don’t like anyway, so it may as well be some reasonable (if not preferable) standard that everyone is using.
Looking at code on somebody else’s screen is entirely missing the point of using tabs over spaces. The entire point is that mine looks like how I want and theirs looks like how they want even though the file is identical. We can each have wildly different tab width yet it’ll look wildly different to each of us when we program. That’s again the point.
Code formatters are great! I love them. Using tabs over spaces is objectively a better formatting option. One of my favorite features in code formatters is that they’ll swap out spaces to tabs for you insane people who insist on mashing the space bar to indent.
No, it’s not missing the point. The premise that you’re always looking at code on the same screen is false, and you don’t always have control over how all screens are configured.
Umm, you do realize no one manually enters all of the spaces, right? Basically all editors support an expandtab feature which inserts the amount of spaces you want whenever you hit the tab key.
Code formatters behave exactly the same regardless if you’re using tabs or spaces, so not sure what you’re talking about.
I did not miss the point. I fully understand that’s why people want tabs. I just think it’s a pretty stupid and petty reason to make for a worse experience when viewing code in places you don’t control. I still don’t know why using spaces is an issue when we enforce standards in literally every other facet of contributing to a codebase. We enforce coding styles. Indentation is part of the coding style.
An assembler doesn’t have any of the interesting parts of a compiler.
Anyway, the problem with Typescript is that it tends to obscure what’s going on one layer below it in ways that don’t happen in traditional compiled languages. We’ve had decades of development on tools that can work together with traditional compilers. Javascript has not, and there are frequent problems getting different tools at different layers of abstraction to march the same direction.
Discord is a fucking plague. I loathe it for communities. As soon as there are more than 10 people in a room, no one can follow what anyone is saying. Threads? No dude, this isn’t the 90s! Let’s slack it up!!! 🤮
A bunch of the servers I’m on actively discourage the use of threads. No idea why. In a different server I’m on, an admin creates a thread for every post in general, so that people can talk about the post without cluttering up the main thread. I wish more servers followed that example.
Are we confusing threaded chat conversations with Threads, the FB/Snap Twitter with dreams of usurping federation to reach new ad contacts; or is it just me?
How the heck slack better or even have any more features than discord? Discord saves all history. Discord has threads that are easier to find than slack threads. Discord voice channels let you just hop in. Discord lets you direct reply.
I use slack for work, but Discord is great for what it is. The search is amazing.
All chat tools after irc have been trash for large communities. That includes slack. Irc somehow still works with 1500 people in it. I can not explain how. With a logging bot the discussions can be archived for google searchabillity. I guess that could be true for a discord or slack also, But i never seen it implemented. In most slacks i can not search more then 60 days back.
I wonder if it works like IRC. The “plague” this entire time has been servers. As soon as the idea only works because somebody, somewhere, is maintaining a server, cloud or hardware, then you’re kinda sunk. The server is the bottleneck. I don’t know how many times I’ve seen a AAA game launch only for the servers to be inadequate. It happens again and again and again, so I assume the business considerations push them toward having just enough server and maybe a little less, never extra, which costs money and cuts margins.
Somewhere there are a bunch of servers howling away in a room that are actually Discord, and Discord spends money to make them howl, so there’s never as much server as you want, which is why things start bogging down with too many people in the chat room at once.
Most importantly to a corporation, if you have to interact with their servers in order to do anything, then they can own the platform by owning the servers. So there’s always going to be a server, even if it’s not strictly needed. The same consideration goes through the head of the streamer who always wants to launch a Discord because it’s “free” but they can sell it to you and then have top level control of an entire community as an asset that can be sold to others. There’s always a server. There will be a server if the actual application doesn’t really need it.
The reason IRC works fine with 1500 people in a chat is because IRC uses the user’s machine for any sort of computation power it needs, and then everything else it is doing is just sending data across wires. There is no central server farm. I haven’t used IRC in a really, really long time, but if it hasn’t changed, then it also doesn’t support lots of picture posting, which helps. Most of the memory usage on my machine at idle is just too many Discord channels all needing to use my local RAM memory to store the umpteen thousand photos everyone has uploaded, all the memes and etc. The IRC I remember was text, and text uses so little data that it can be treated like zero data.
Lots of pictures are probably non-negotiable in the modern era. Heck, they’re pretty important for serious work tasks, like putting up a shot of the broken gadget, so the engineering team can get an eyeball on the failure, that means pictures are in, text-only isn’t viable. I don’t know if modern IRC supports this or not, it probably does if people are still using it at all.
But IRC is a piece of open-source software that you install on your machine, free to the user. It’s not a web app, it doesn’t live in a browser. The data of you interacting with others is being sent out to them and also back to you, where it shows up in your IRC client and the chat room. If 1500 people are using it, then 1500 people have each added some of their machine power to making it all work, so it scales, it always has as much hardware as it needs. Again, there’s no server in the middle to run out of capacity, so that problem is just bypassed.
Everything used to work like this, circa the late 1990s and early 2010s. Everyone was assumed to be on a PC of their own, and the only problem was how to connect them together to do stuff, like have deranged fan wars about shows. BBSs were already kind of old hat, and there’s that damn server again, every BBS has one. All the most clever apps of the 90s, even the web, managed to jump through hoops to avoid the necessity of a central server to get things done because then somebody has to pay for it, run it, maintain it and own it. We just want the wires, the lovely, lovely cables dragged across the sea at somebody else’s unthinkable expense. If you can eliminate the server somehow, then you win. And they did. Things like IRC and ICQ blew the hell up from using that model.
We really need to dig that entire concept back up and brush the dust off of it. I wonder if that’s what Matrix is.
Now if you’ll excuse me I need to go prune some pointless Discord channels. Oh, by the by, fucking nobody uses Slack, or knows what it is. Dudes on the internet all think it’s normal because tech offices seem to use it a lot, the rest of the world has never used Slack. Up until right now I was assuming that Discord and Slack are the same thing, owned by the same company, and Slack is just the “business casual” version of Discord. This doesn’t seem to be true, but that’s how unfamiliar I am with Slack, while being chronically online. There are probably more people around who still remember ICQ than have ever used Slack in their lives.
I love the Church of the Subgenius reference built into Slack’s name. From what I can tell, nobody who uses that thing actually gets any slack, it actively removes slack from your life and makes boss surveillance really, really easy for the boss, but you must always act as though Big Brother can hear, or you’re fucked. Good work Bob, nice joke. Anyway, I shut up now.
I found IRC loses chat flow more easily, as actual chat gets lost in the stream of blabber.
I am intrigued to see how threaded conversations in slack et al work, but haven’t been at a shop where slack was allowed as a tool due to data sovereignty and the CLOUD act.
But IRC was always something I approached reluctantly, and that’s been 31 years now.
It also seems to attract a younger crowd - I had to state my age to join one server and the mod screenshotted my info and everyone laughed calling me “boomer”. I’m only 40 (Millennial) and it wasn’t a gaming or specifically teen-server. It was a silly ironic European Reddit server.
The subreddit seems to have a range of ages. The Discord server is a bunch of kids commenting capybara and cat emojis like it’s funny. :/
I dunno why but they wanted you to comment your name, age and location in a welcome channel. I did and they screenshot and shared it in the main channel. Most of the people are around 16-19 with a few 20-25yo. I didn’t know that til I joined though!
I was very weird to be there apparently.
I just wanted to take the piss out of Europeans. There’s no age-limit in that.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.