Interesting ideas. Since you haven't been around here as long as us (*cough*) old-timers, you've probably not read the posts about how the hardware and site is essentially free to us (but please find the donut button), and updates are by people with real jobs who help out because they have the skills, motivation, and time to do so. It's supposed to be a lean mean content site. As such, it should load very quickly on a phone, assuming a few personalized settings to reduce the sidebar clutter.

On my Firefox, the edit box is resizable. I don't look into that sorta stuff much, I take it for granted, so I'm not sure if there are some server side settings that will improve those kinds of issues.

Toolbar? I basically taught myself some HTML by wanting to post here, so I think it's a help, but I can see how someone wouldn't want to remember how to enter a less than or a bullet list. I can only offer that you might write it in something else and paste in the HTML equivalent, complete with custom site tags. Sorry.

I've also seen some folks wrestling with fancy sites that do all that sh*t for you. It's a nightmare, because you need a plugin for this, and a plugin for that, and this plugin isn't compatible with the framework version, or the other plugins you need, or your security plugin, and your hosting service doesn't allow SSH except from registered IPs and Tuesdays in months with the letter A in them. So the people with the most motivation to contribute content spend most of their time keeping the system from crashing, burn out, and find something more productive to contribute to.

If you want a pretty site, that's easy for our collective parent-in-laws to use, please feel free to start one. But this site is the way it is, because it is useful to its members, and has a reasonable barrier to entry for mischief makers. There's also some degree of growing into the community, by fiddling with all the knobs (and being told you're a knob sometimes).

Seriously, the only thing I've felt a very small need for is some image capability. But everyone seems to find someplace to host a screenshot or a big text dump, at least for a short time. Since the site hardware is essentially provided for free, I wouldn't want to waste storage space on cat videos for the sake of the rare screenshot.

But if you have a burning Perl question (and sometimes not even Perl), and you want a quick, accurate, efficient answer (really, all three are available most of the time), post your question here. I've had little questions that had 10 replies in 15 minutes, which unblocked my $work, and made me look impressive in the eyes of the boss. (Thanks to all of those responders over the years who have helped me out, put up with my stupidity, and let me post more questions and answers anyway!)

So please don't take this the wrong way. Many have come and said "Why are you so far behind?" And the answer has always been, "Why do we need more than this?". It's like NASA spending millions to develop a zero-G ballpoint pen, while the Russians are using pencils. We like suggestions, and we consider all reasonable ideas (and sometimes the unreasonable ones). Then like anything else, it comes down to what to do, who has the skill, and who has the time. Many "nice to have" ideas have fallen by the wayside for lack of any of those three points. Mostly we only need pencils here. Sometimes we'd like to have zero-G ballpoint laser GPS quantum tunneling time machine teleporting 3D printers. But then we'd become rich and famous, and we couldn't stand for that.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.