Handling cases where Javascript is turned off [closed]Browser statistics on JavaScript disabledCreate GUID / UUID in JavaScript?How do JavaScript closures work?What is the most efficient way to deep clone an object in JavaScript?How do I remove a property from a JavaScript object?Which equals operator (== vs ===) should be used in JavaScript comparisons?How do I include a JavaScript file in another JavaScript file?What does “use strict” do in JavaScript, and what is the reasoning behind it?How to check whether a string contains a substring in JavaScript?How do I remove a particular element from an array in JavaScript?For-each over an array in JavaScript?
What to call a small, open stone or cement reservoir that supplies fresh water from a spring or other natural source?
Why is there no current between two capacitors connected in series?
Is there a way to generate a mapping graph like this?
Connecting circles clockwise in TikZ
How could Dwarves prevent sand from filling up their settlements
why "American-born", not "America-born"?
Was murdering a slave illegal in American slavery, and if so, what punishments were given for it?
Why "strap-on" boosters, and how do other people say it?
Presenting 2 results for one variable using a left brace
Is there a realtime, uncut video of Saturn V ignition through tower clear?
Is my company merging branches wrong?
Filter a file list against an integer array?
How do we properly manage transitions within a descriptive section?
Separate the element after every 2nd ',' and push into next row in bash
Why did Nick Fury not hesitate in blowing up the plane he thought was carrying a nuke?
What Species of Trees are These?
Do 'destroy' effects count as damage?
Do most Taxis give Receipts in London?
How to play vs. 1.e4 e5 2.Nf3 Nc6 3.Bc4 d6?
Why does an injection from a set to a countable set imply that set is countable?
How did Jean Parisot de Valette, 49th Grand Master of the Order of Malta, die?
Mikrokosmos, BB 105, Vol. 1: No. 17 Contrary Motion (1) - Can't understand the structure
Requirement for splicing neutrals in a switch
How could the B-29 bomber back up under its own power?
Handling cases where Javascript is turned off [closed]
Browser statistics on JavaScript disabledCreate GUID / UUID in JavaScript?How do JavaScript closures work?What is the most efficient way to deep clone an object in JavaScript?How do I remove a property from a JavaScript object?Which equals operator (== vs ===) should be used in JavaScript comparisons?How do I include a JavaScript file in another JavaScript file?What does “use strict” do in JavaScript, and what is the reasoning behind it?How to check whether a string contains a substring in JavaScript?How do I remove a particular element from an array in JavaScript?For-each over an array in JavaScript?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I did some Javascript back in the late 90s and got moderately fluent with it but finally drifted away because it was such a pain to make it work right in various different browsers, each of which had their own eccentricities. A lot has changed since those days with the advent of JQuery and various Javascript frameworks. I'm toying with the idea of getting back into Javascript, perhaps via JQuery or one of the frameworks, but I've got one fundamental question that I need to have answered before I decide: do all Javascript developers simply assume that Javascript is turned on in their users' browsers? If not, how are they handling users who DON'T have Javascript turned on?
Back when I used Javascript, you used the NOSCRIPT tag to tell people that the page wouldn't work and, in effect, told them to turn on Javascript or don't bother staying on this webpage because it wasn't going to work for them. Is that still the basic approach?
One other related question: just how common is it for people to have Javascript turned off these days? Or to put it another way, what are the most common situations where people have Javascript turned off?
Putting on a project manager hat, if I were trying to choose how to build a website and selecting the tools/technology, I think I'd be quite reluctant to use Javascript if a significant part of the user base was going to have Javascript turned off. That would ensure that some significant number of people weren't going to see/use the pages I was creating OR it would force me to do everything TWICE, once in Javascript and once in some other language. (For instance, I could have a form and do validations in Javascript when people had it turned on but do equivalent validations in something like PHP for those who have Javascript turned off.) Losing a bunch of users is not likely to be satisfactory to whoever wants me to build this website and having to do everything twice is not going to be a positive thing for my development budget because I've got twice as much code to design, develop, test and maintain and would very possibly make me hire more people to do the work.
I'd like to know just how people rationalize using Javascript in 2019. I know Javascript is widely used so the benefits must still outweigh the negatives. I just want to know what the arguments are for using Javascript despite the negatives.
javascript
asked Mar 23 at 19:51
HenryHenry
584413
closed as primarily opinion-based by Robert Harvey♦ Mar 23 at 20:03
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 2 more comments
I did some Javascript back in the late 90s and got moderately fluent with it but finally drifted away because it was such a pain to make it work right in various different browsers, each of which had their own eccentricities. A lot has changed since those days with the advent of JQuery and various Javascript frameworks. I'm toying with the idea of getting back into Javascript, perhaps via JQuery or one of the frameworks, but I've got one fundamental question that I need to have answered before I decide: do all Javascript developers simply assume that Javascript is turned on in their users' browsers? If not, how are they handling users who DON'T have Javascript turned on?
Back when I used Javascript, you used the NOSCRIPT tag to tell people that the page wouldn't work and, in effect, told them to turn on Javascript or don't bother staying on this webpage because it wasn't going to work for them. Is that still the basic approach?
One other related question: just how common is it for people to have Javascript turned off these days? Or to put it another way, what are the most common situations where people have Javascript turned off?
Putting on a project manager hat, if I were trying to choose how to build a website and selecting the tools/technology, I think I'd be quite reluctant to use Javascript if a significant part of the user base was going to have Javascript turned off. That would ensure that some significant number of people weren't going to see/use the pages I was creating OR it would force me to do everything TWICE, once in Javascript and once in some other language. (For instance, I could have a form and do validations in Javascript when people had it turned on but do equivalent validations in something like PHP for those who have Javascript turned off.) Losing a bunch of users is not likely to be satisfactory to whoever wants me to build this website and having to do everything twice is not going to be a positive thing for my development budget because I've got twice as much code to design, develop, test and maintain and would very possibly make me hire more people to do the work.
I'd like to know just how people rationalize using Javascript in 2019. I know Javascript is widely used so the benefits must still outweigh the negatives. I just want to know what the arguments are for using Javascript despite the negatives.
javascript
asked Mar 23 at 19:51
HenryHenry
584413
closed as primarily opinion-based by Robert Harvey♦ Mar 23 at 20:03
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
1
The argument for using Javascript is simple: it gives you programmatic capability in the browser. Tell your users to ditch Windows XP and get with the times.
– Robert Harvey♦
Mar 23 at 19:53
Good way to start is get more informations about Progressive Web Apps.
– Kamil Naja
Mar 23 at 19:54
Lots of questions there. Look here. This might answer a few, though it doesn't go into programming in JS in depth.
– Chipster
Mar 23 at 19:55
1
do all Javascript developers simply assume that Javascript is turned on in their users' browsers In today's world, turning JavaScript off is tantamount to breathing without oxygen. This is a non-issue. JavaScript is a fundamental component of the web.
– Scott Marcus
Mar 23 at 20:08
Progressive enhancement is still a best practice. Unfortunately many devs are abandoning it because using a clientside JS framework is simpler (read: cheaper) than doing rendering both on server and client. As always, the answer is It depends - on the audience, the content, and the features you want to implement.
– Bergi
Mar 23 at 20:15
|
show 2 more comments
I did some Javascript back in the late 90s and got moderately fluent with it but finally drifted away because it was such a pain to make it work right in various different browsers, each of which had their own eccentricities. A lot has changed since those days with the advent of JQuery and various Javascript frameworks. I'm toying with the idea of getting back into Javascript, perhaps via JQuery or one of the frameworks, but I've got one fundamental question that I need to have answered before I decide: do all Javascript developers simply assume that Javascript is turned on in their users' browsers? If not, how are they handling users who DON'T have Javascript turned on?
Back when I used Javascript, you used the NOSCRIPT tag to tell people that the page wouldn't work and, in effect, told them to turn on Javascript or don't bother staying on this webpage because it wasn't going to work for them. Is that still the basic approach?
One other related question: just how common is it for people to have Javascript turned off these days? Or to put it another way, what are the most common situations where people have Javascript turned off?
Putting on a project manager hat, if I were trying to choose how to build a website and selecting the tools/technology, I think I'd be quite reluctant to use Javascript if a significant part of the user base was going to have Javascript turned off. That would ensure that some significant number of people weren't going to see/use the pages I was creating OR it would force me to do everything TWICE, once in Javascript and once in some other language. (For instance, I could have a form and do validations in Javascript when people had it turned on but do equivalent validations in something like PHP for those who have Javascript turned off.) Losing a bunch of users is not likely to be satisfactory to whoever wants me to build this website and having to do everything twice is not going to be a positive thing for my development budget because I've got twice as much code to design, develop, test and maintain and would very possibly make me hire more people to do the work.
I'd like to know just how people rationalize using Javascript in 2019. I know Javascript is widely used so the benefits must still outweigh the negatives. I just want to know what the arguments are for using Javascript despite the negatives.
javascript
asked Mar 23 at 19:51
HenryHenry
584413
I did some Javascript back in the late 90s and got moderately fluent with it but finally drifted away because it was such a pain to make it work right in various different browsers, each of which had their own eccentricities. A lot has changed since those days with the advent of JQuery and various Javascript frameworks. I'm toying with the idea of getting back into Javascript, perhaps via JQuery or one of the frameworks, but I've got one fundamental question that I need to have answered before I decide: do all Javascript developers simply assume that Javascript is turned on in their users' browsers? If not, how are they handling users who DON'T have Javascript turned on?
Back when I used Javascript, you used the NOSCRIPT tag to tell people that the page wouldn't work and, in effect, told them to turn on Javascript or don't bother staying on this webpage because it wasn't going to work for them. Is that still the basic approach?
One other related question: just how common is it for people to have Javascript turned off these days? Or to put it another way, what are the most common situations where people have Javascript turned off?
Putting on a project manager hat, if I were trying to choose how to build a website and selecting the tools/technology, I think I'd be quite reluctant to use Javascript if a significant part of the user base was going to have Javascript turned off. That would ensure that some significant number of people weren't going to see/use the pages I was creating OR it would force me to do everything TWICE, once in Javascript and once in some other language. (For instance, I could have a form and do validations in Javascript when people had it turned on but do equivalent validations in something like PHP for those who have Javascript turned off.) Losing a bunch of users is not likely to be satisfactory to whoever wants me to build this website and having to do everything twice is not going to be a positive thing for my development budget because I've got twice as much code to design, develop, test and maintain and would very possibly make me hire more people to do the work.
I'd like to know just how people rationalize using Javascript in 2019. I know Javascript is widely used so the benefits must still outweigh the negatives. I just want to know what the arguments are for using Javascript despite the negatives.
javascript
javascript
asked Mar 23 at 19:51
HenryHenry
584413
asked Mar 23 at 19:51
HenryHenry
584413
asked Mar 23 at 19:51
HenryHenry
584413
asked Mar 23 at 19:51
HenryHenry
584413
asked Mar 23 at 19:51
HenryHenry
584413
584413
closed as primarily opinion-based by Robert Harvey♦ Mar 23 at 20:03
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as primarily opinion-based by Robert Harvey♦ Mar 23 at 20:03
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
1
The argument for using Javascript is simple: it gives you programmatic capability in the browser. Tell your users to ditch Windows XP and get with the times.
– Robert Harvey♦
Mar 23 at 19:53
Good way to start is get more informations about Progressive Web Apps.
– Kamil Naja
Mar 23 at 19:54
Lots of questions there. Look here. This might answer a few, though it doesn't go into programming in JS in depth.
– Chipster
Mar 23 at 19:55
1
do all Javascript developers simply assume that Javascript is turned on in their users' browsers In today's world, turning JavaScript off is tantamount to breathing without oxygen. This is a non-issue. JavaScript is a fundamental component of the web.
– Scott Marcus
Mar 23 at 20:08
Progressive enhancement is still a best practice. Unfortunately many devs are abandoning it because using a clientside JS framework is simpler (read: cheaper) than doing rendering both on server and client. As always, the answer is It depends - on the audience, the content, and the features you want to implement.
– Bergi
Mar 23 at 20:15
|
show 2 more comments
1
The argument for using Javascript is simple: it gives you programmatic capability in the browser. Tell your users to ditch Windows XP and get with the times.
– Robert Harvey♦
Mar 23 at 19:53
Good way to start is get more informations about Progressive Web Apps.
– Kamil Naja
Mar 23 at 19:54
Lots of questions there. Look here. This might answer a few, though it doesn't go into programming in JS in depth.
– Chipster
Mar 23 at 19:55
1
do all Javascript developers simply assume that Javascript is turned on in their users' browsers In today's world, turning JavaScript off is tantamount to breathing without oxygen. This is a non-issue. JavaScript is a fundamental component of the web.
– Scott Marcus
Mar 23 at 20:08
Progressive enhancement is still a best practice. Unfortunately many devs are abandoning it because using a clientside JS framework is simpler (read: cheaper) than doing rendering both on server and client. As always, the answer is It depends - on the audience, the content, and the features you want to implement.
– Bergi
Mar 23 at 20:15
1
1
The argument for using Javascript is simple: it gives you programmatic capability in the browser. Tell your users to ditch Windows XP and get with the times.
– Robert Harvey♦
Mar 23 at 19:53
The argument for using Javascript is simple: it gives you programmatic capability in the browser. Tell your users to ditch Windows XP and get with the times.
– Robert Harvey♦
Mar 23 at 19:53
Good way to start is get more informations about Progressive Web Apps.
– Kamil Naja
Mar 23 at 19:54
Good way to start is get more informations about Progressive Web Apps.
– Kamil Naja
Mar 23 at 19:54
Lots of questions there. Look here. This might answer a few, though it doesn't go into programming in JS in depth.
– Chipster
Mar 23 at 19:55
Lots of questions there. Look here. This might answer a few, though it doesn't go into programming in JS in depth.
– Chipster
Mar 23 at 19:55
1
1
do all Javascript developers simply assume that Javascript is turned on in their users' browsers In today's world, turning JavaScript off is tantamount to breathing without oxygen. This is a non-issue. JavaScript is a fundamental component of the web.
– Scott Marcus
Mar 23 at 20:08
do all Javascript developers simply assume that Javascript is turned on in their users' browsers In today's world, turning JavaScript off is tantamount to breathing without oxygen. This is a non-issue. JavaScript is a fundamental component of the web.
– Scott Marcus
Mar 23 at 20:08
Progressive enhancement is still a best practice. Unfortunately many devs are abandoning it because using a clientside JS framework is simpler (read: cheaper) than doing rendering both on server and client. As always, the answer is It depends - on the audience, the content, and the features you want to implement.
– Bergi
Mar 23 at 20:15
Progressive enhancement is still a best practice. Unfortunately many devs are abandoning it because using a clientside JS framework is simpler (read: cheaper) than doing rendering both on server and client. As always, the answer is It depends - on the audience, the content, and the features you want to implement.
– Bergi
Mar 23 at 20:15
|
show 2 more comments
1 Answer
1
active
oldest
votes
(Strong use of exageration ahead)
If you care about reaching a sizable audience:
Everyone uses Javascript. It is everywhere. Everyone has it turned on.
<noscript> comes in handy for web crawlers.
No one builds sites intended for human users with <noscript> anymore.
There is also this:
Browser statistics on JavaScript disabled
This is also interesting:
https://www.screamingfrog.co.uk/crawl-javascript-seo/
answered Mar 23 at 19:59
DavidDavid
1,32311326
1
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
1
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
(Strong use of exageration ahead)
If you care about reaching a sizable audience:
Everyone uses Javascript. It is everywhere. Everyone has it turned on.
<noscript> comes in handy for web crawlers.
No one builds sites intended for human users with <noscript> anymore.
There is also this:
Browser statistics on JavaScript disabled
This is also interesting:
https://www.screamingfrog.co.uk/crawl-javascript-seo/
answered Mar 23 at 19:59
DavidDavid
1,32311326
1
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
1
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
add a comment |
(Strong use of exageration ahead)
If you care about reaching a sizable audience:
Everyone uses Javascript. It is everywhere. Everyone has it turned on.
<noscript> comes in handy for web crawlers.
No one builds sites intended for human users with <noscript> anymore.
There is also this:
Browser statistics on JavaScript disabled
This is also interesting:
https://www.screamingfrog.co.uk/crawl-javascript-seo/
answered Mar 23 at 19:59
DavidDavid
1,32311326
1
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
1
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
add a comment |
(Strong use of exageration ahead)
If you care about reaching a sizable audience:
Everyone uses Javascript. It is everywhere. Everyone has it turned on.
<noscript> comes in handy for web crawlers.
No one builds sites intended for human users with <noscript> anymore.
There is also this:
Browser statistics on JavaScript disabled
This is also interesting:
https://www.screamingfrog.co.uk/crawl-javascript-seo/
answered Mar 23 at 19:59
DavidDavid
1,32311326
(Strong use of exageration ahead)
If you care about reaching a sizable audience:
Everyone uses Javascript. It is everywhere. Everyone has it turned on.
<noscript> comes in handy for web crawlers.
No one builds sites intended for human users with <noscript> anymore.
There is also this:
Browser statistics on JavaScript disabled
This is also interesting:
https://www.screamingfrog.co.uk/crawl-javascript-seo/
answered Mar 23 at 19:59
DavidDavid
1,32311326
edited Mar 23 at 20:13
answered Mar 23 at 19:59
DavidDavid
1,32311326
answered Mar 23 at 19:59
DavidDavid
1,32311326
answered Mar 23 at 19:59
DavidDavid
1,32311326
1,32311326
1
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
1
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
add a comment |
1
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
1
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
1
1
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Most web crawlers can handle javascript since they use a headless browser to gather the data.
– Get Off My Lawn
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
Hah, I was just editing in that last link about the SEO aspects, and how they have changed.
– David
Mar 23 at 20:02
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
I dabbled with some of that old #! stuff back in the day, and it was a real pain.
– David
Mar 23 at 20:03
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
Everyone is wrong. There is definitely a minority who still uses noscript, scriptsafe or similar browser plugins to only allow js on selected pages, for fear of spectre or something else. I can't tell how large this minory is, though.
– Bergi
Mar 23 at 20:05
1
1
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
I've edited, to call out what I thought was obvious use of hyperbole. Although, in the spirit of trying to help the user asking the question, I can't in good faith recommend handling that small percent of users for most practical applications.
– David
Mar 23 at 20:10
add a comment |
1
The argument for using Javascript is simple: it gives you programmatic capability in the browser. Tell your users to ditch Windows XP and get with the times.
– Robert Harvey♦
Mar 23 at 19:53
Good way to start is get more informations about Progressive Web Apps.
– Kamil Naja
Mar 23 at 19:54
Lots of questions there. Look here. This might answer a few, though it doesn't go into programming in JS in depth.
– Chipster
Mar 23 at 19:55
1
do all Javascript developers simply assume that Javascript is turned on in their users' browsers In today's world, turning JavaScript off is tantamount to breathing without oxygen. This is a non-issue. JavaScript is a fundamental component of the web.
– Scott Marcus
Mar 23 at 20:08
Progressive enhancement is still a best practice. Unfortunately many devs are abandoning it because using a clientside JS framework is simpler (read: cheaper) than doing rendering both on server and client. As always, the answer is It depends - on the audience, the content, and the features you want to implement.
– Bergi
Mar 23 at 20:15