justsomehnguy
They always can take the matter in their hands. Worked wonders in Europe the last fifteen years.
Yes, by being the great equalizer. But the question is why WASD and not something else eg WSDX[0] or some shit like ASDF. And the ghosting explains it well enough.
And this is exactly the same with ESDF.
You would be quite astonished by the fact what I do not actually saying that. More so, I don't even imply it. But thanks for thinking and speaking instead of me.
> The Brainiest Club in the World - Yale University Press
No.
> • Total
> 6,973,333[3]
Works for Indiana, good. But I doubt it scales.
That's because you are just accustomed to it [0]. If you would have a fresh look on it, especially on a small screen - it would find it atrocious.
There is still a separate SMTP configuration and it's a separate separate SMTP configuration for the each account.
There is absolutely useless left vertical bar which... does nothing what can't be shoved unto the useless, empty top bar. There is useless empty top bar which holds a search box and a hamburger menu.
For the unknown reason[1] this top bar is twice the tall of the regular menu. Oh. There is TWO search boxes[2]. Enabling Quick Filter adds another toolbar instead of using the bar where the button 'Quick Filter' resides.
And if you have multiple accounts and for some reason you can't auth for a moment (eg server problem, not with a connection) you would be spammed with the auth boxes and even if you successfully auth in one - you would still need to cancel or auth in all other what was spammed on you.
There is a lot, a lot of things where TB sucks. You just familiar with it.
[0] and probably configured it years ago and never touched the config too.
[1] actually it to be tall enough to hold hamburger button - because there is an option to add buttons to it. But you can't move buttons from the left useless vertical bar to the top bar. So you can have 'Mail', 'Calendar' etc duplicated on the top bar... for what?
NB yes you can hide the left vertical bar. Hide, not remove. Still it was thought on, implemented and shoved on our asses for absolutely no reason..
For the games. Some games and 'media' programs like encyclopedias did require it run.
Would it change anyhthing? No. Because developers of the programs what are not part of Windows aren't keen on keeping "the same efficiency". Audacity 4, Thunderbird are good examples of a bad interface - and they did it disregarding the OS UI.
Now, considering you don't even know me: go in the bathroom, look atvthe mirror and repeat your comment.
Come back when the enlightment hit you.
is the key here
the same reason WhatsApp and Telegram won on their markets
Elon Musk and the whole capital serving US government is not a good outcome.
There was a fun take on it on r/comics recently: https://www.reddit.com/r/comics/comments/1x4toay/the_day_all...
> business owners benefit because the people they can hire from are healthier, so more productive.
As we can see now - capitalism would prefer "stupid", way productive robots running 24/7 in a dark warehouses to a healthier, more productive population. Lighting savings are already cover most of difference (/s but only so slightly).
dns_snek: and macvlan is not called a bridge because it uses a Linux bridge you stupid
dns_snek: I'm a good boy and always right!
^ that's you
pat pat
I think you are the one who built an alternate layering system? On mobile, don't like to search rn.
If yes the basics are in the first comment- just not limited to the one RUN statement ofc. And if I do remember how the layers are made then making it transaction-like would be a great dedup saver eg for adding a static rarely changed artifacts - there could be essentially a ~one layer for how many you want images.
Implementation wouldn't be so difficult - you just stop committing until TRAN END; but the main is too provide a mental model for a not very experiencied dev how this supports his work and makes it more efficient on the storage and execution.
> what was holding them back?
Did you miss 'up to 30 secs' in the previous comment? It's not about lighthouse scores. It's the whole feeling of a hodge-podged project which is run by people who are - maybe - passionate but ultimately lacking in the basics.
The ultimate buyers of their product was the system operators and the system owners - not the developers per se. They failed hard everything that space. Having a dog slow the main content site didn't added anything positive.
Sorry, but you do insist on naming 'docker' bridge a bridge because it's underlying tech is a bridge. Make up your mind.
> A Docker 'bridge' network driver creates a broadcast domain between containers attached to that network.
And noone absolutely ever cared about what it's a bridge down there. It could be using gronklew and maybe 20 people on the planet would care to learn what it is.
You are quite bent on it, but nobody cares how the containers talk between each other.
> Why do you expect it to join the broadcast domains of your containers and your LAN?
I expect a setting named 'bridge' in some $thing to actually implement a bridge.
Just like you pressing an AC button in your car expect a very specific thing to turn on/off and not 'Artifically flavoured windshield wipers served in a Container'.
Why do I want it is on me. Maybe I need it. Maybe I control my network and freely give out addresses to anything. Maybe I don't run on some cheap VPS somewere with only 1 IP I can't choose nor change. Bazillion of options. None matters because this is not about 'why do you want it'.
> And which LAN, exactly?
The path of a least automagik.
Only one ethernet interface? Then connect to that ethernet interface. Bitch in the logs what automagik was used and this can lead to the problems.
Many interfaces? Just shutdown (least pain for newbies) or start without attaching (harder to troubleshoot for newbies). Bitch in the logs in either case.
> Your misunderstanding seems to stem from the flawed assumption/expectation that every container is automatically attached to your LAN
'Your misunderstanding seems to stem what there are some people assume what they are driving in like c-a-a-r. When even 5y.o. knows it's the wheels what drives you around.'
> Docker networks are entities independent of your LAN, they're isolated networks that primarily serve to connect containers amongst themselves.
Yes, exactly. Don't call it 'bridge' ~20 years ago and we don't have this talk here.
> Auto-configuration of NAT between the internal bridge network and your LAN is just a convenience feature which you can disable, it's not an inherent property of bridge networks.
It's not even a property of a bridge network. For someone claming knowledge superiority this is a quite lame statement.
> links
Really.
> previous experience in an adjacent area where
Ah, yes, irrelevant 'adjacent area' of computer networks. I'm out of words.[0]
> All of this networking terminology is consistent and applied correctly
No. Go drive your wheels home.
> Don't shift the goalposts. You claimed it still doesn't exist.
I'm just mentioned RUN as an example. You decided what multiline is the goalpost.
And yes, if even the official Docker images doesn't use RUN heredocs then... there is something wrong with them. Like being implemented too late.
[0] but perfectly explains your previous 'flawed assumption'
Oh, well. I guess you ride to your work on wheels, right? Because while you sit in the car/bus/train it's the wheels what actually rides on the road/track, right?
And if you bothered to look at that comment then why do you ignore what 'macvlan' - which is an actual bridge both in terms of a Linux device and the functionality - is not called 'bridge'?
Because you don't understand the problem. More so, you ignore the actual question there about the broadcast domains.
No, if even if you use a bridge internally when your container is on a isolated network which is invisible to anyone on your network and the container access the network behind your host through the NAT - this can't be called a bridge.
You see, if they just called it as it should, ig:
bridge => hostnatnetwork // or internalbridgenatnetwork or whatever else
macvlan => bridge
But the last 1% is the people who actually makes the workspaces for these developers where they actually do run their fancy-shmancy containers. And for that 1% it surely pays naming this as they are.
And there is also that dumb decision to silently rewrite 127.0.0.1 to Google DNS without a question. Especially when 98% of Docker users are incapable to diagnose it by themselves.
So it's not only the naming of a network functions.
But hey, I'm just knowledge lacking guy without experience at all, just yesterday saw a computer a first time in my life, sure, sure.
> RUN command has had heredoc support for 5 years now
So ten years late? Adoption is off the limits, as you can see - that snippet is from the official Docker image.
And if I need to run multiple commands and not just one RUN statement? Like the people are asking for years? And you so knowledgeable person of course do know the reason for that, right?
That's because there was never a proper sysadmin on your team to slap some sense in your decisions.
You've got too opinionated[0], too tied on yourself[1] monster which required too much resources what you can handle alone.
And your market is not the developers but the companies where whose developers have a daytime jobs: https://news.ycombinator.com/item?id=34377674
BTW just for giggles opened hub.docker.com with Network Tools opened:
368 requests, 9.62MB, Finish: 4.50s.
For a thing which should be a static cached copy with everything bundled. Sure, it's a progress from the previous iterations when it could hang for 30 seconds before actually loading... but this is still ridiculous.
[0] https://news.ycombinator.com/item?id=46739153
[1] Eg: the syntax to point the image to a specific registry is something... bad. So bad I just abandoned running my own registry, it wasn't worth it.
PS there is still (AFAIK) no support for a transaction-like image building in Compose. So instead of something like this:
TRANSACTION START
RUNBATCH set -eux
# TODO find a better userspace architecture detection method than querying the kernel
arch="$(uname -m)"
case "$arch" in \
aarch64) gosuArch='arm64' ;
x86_64) gosuArch='amd64' ;
*) echo >&2 "error: unsupported architecture: '$arch'"; exit 1 ;
esac
curl -fL -o /usr/local/bin/gosu.asc "https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$gosuArch.asc"
curl -fL -o /usr/local/bin/gosu "https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$gosuArch"
export GNUPGHOME="$(mktemp -d)"
gpg --batch --keyserver hkps://keys.openpgp.org --recv-keys B42F6819007F00F88E364FD4036A9C25BF357DD4
gpg --batch --verify /usr/local/bin/gosu.asc /usr/local/bin/gosu
rm -rf "$GNUPGHOME" /usr/local/bin/gosu.asc
chmod +x /usr/local/bin/gosu
gosu --version
gosu nobody true
TRANSACTION END
RUN set -eux; \
# TODO find a better userspace architecture detection method than querying the kernel
arch="$(uname -m)"; \
case "$arch" in \
aarch64) gosuArch='arm64' ;; \
x86_64) gosuArch='amd64' ;; \
*) echo >&2 "error: unsupported architecture: '$arch'"; exit 1 ;; \
esac; \
curl -fL -o /usr/local/bin/gosu.asc "https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$gosuArch.asc"; \
curl -fL -o /usr/local/bin/gosu "https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$gosuArch"; \
export GNUPGHOME="$(mktemp -d)"; \
gpg --batch --keyserver hkps://keys.openpgp.org --recv-keys B42F6819007F00F88E364FD4036A9C25BF357DD4; \
gpg --batch --verify /usr/local/bin/gosu.asc /usr/local/bin/gosu; \
rm -rf "$GNUPGHOME" /usr/local/bin/gosu.asc; \
chmod +x /usr/local/bin/gosu; \
gosu --version; \
gosu nobody true
And when people cried what 'oh noes i cant find a needed program in that awful fullscreen start menu uwu' I just show my Vista Start Menu list which took 4 FullHD screen heights on the small font settings.
And as people in the nearby comments say the problem here is what there is a lot of newcomers who just do shit - by mere lack of knowledge or worse by being KPI driven. Just like the last update of Mozilla Firefox which added ellipsised tabs. Like... for what? On the desktop?
> As a journalist ... It was at the three-day Munich Security Conference that ended on February 20 2022
Ah yes, nothing was happening in the world in previous 30 years and some countries absolutely didn't insist on being involved in the military conflicts on the other side of the globe. Nothing happened and it was kumbyaya everywhere. And no civilian casulties, of course.