thinkxl

old thread about the same with good examples: https://news.ycombinator.com/item?id=6005295

Looks like you are getting downvoted. I upvoted you, so I'll leave this here because is relevant: https://sonniesedge.co.uk/posts/progressive-enhancement

Come on, the website is only text, images, and a few forms, why would you render it in JavaScript. I don't see any additional benefit compared with plain HTML, CSS.

It is not a rich web application, even if it were.

Also, there's been server-side rendering for a while now.

Edit: Opinion

So, I'll give some unsolicited recommendations for your website, regarding accessibility:

- The contrast between the body text and background is to low; it makes it difficult for people with visual impairments to use the website.

- Font size and font weight, the font is too thin and adding this to the low color contrast, it makes it even more difficult to read.

- Images that don't add meaning (textually) to the page, e.g., the logos you use on the "Agile and precise" section. It's a good idea to add `aria-hidden="true"` so they don't "distract" screen readers.

- Also, several images don't have their alt tag, which describes the image to screen readers.

- I can't navigate your website with my keyword.

I don't want to sound like a jerk, but your company builds assistive technology--yes, a phone is an assistive device--so it makes sense that you take care of your primary point of sales, your website, and make it accessible to everybody.

You are missing the point; if you use JavaScript, you use prototypal inheritance whether you like it or not, e.g.:

  function getUser() {} 

That is creating an instance of the `Function` constructor object[1][2]. In a Classical (as classes) language, you would see that like this:

  // `Function` being a class 
  function getUser extends Function {}

but because JavaScript is purely prototypal, this works differently.

You say that there's no reason to learn prototypal inheritance, well, the only and valid reason is that to write at least decent JavaScript you have to understand how it works behind the scenes.

* [1] - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

* [2] - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Edit: add links

If you like books, read these in this order:

1. Eloquent JavaScript by Marijn Haverbeke

2. Secrets of the JavaScript Ninja by John Resig (jQuery author) and Bear Bibeault

Those two books formed the foundation for my understanding of JavaScript. Now, I understand any framework or pattern easily.

Edit: format

Prototypal inheritance plays a huge role in understanding the language because JavaScript uses it for everything.

It might be a good idea to learn about this before using ES6 classes; remember that ES6 classes are syntactic sugar on top of prototypal inheritance anyway. They wouldn't learn legacy patterns, but the actual pattern that JavaScript uses.

I use a Thinkpad X220 too.

There's an entire community around getting your Thinkpad the way you want.

One time I had to replace the wireless card and instead of going to a technician or Best Buy I asked in the IRC channel (##ibmthinkpad on Freenode); the people in there gave me instructions and the exact Amazon links for what I needed. It saved me time and money.

- http://x220.mcdonnelltech.com/ubuntu/

- https://www.reddit.com/r/thinkpad/comments/4lwc01/challenge_...

Edit: added some links and IRC channel.

In that example I put the form on the '/' route. Here is a GitHub repo with the code:

https://github.com/thinkxl/hn-bottle-example

And here is a gif showing how it works:

https://dsh.re/364b2

Edit: Words.

Flask is really cool. It has a great community and a package for everything you'd need.

Bottle[0], Dataset[1], and pipenv[3].

With those three tools I can create a web app with basic functionality with few lines of code, like a prototype. For example:

  from datetime import datetime
  from bottle import get, post, request, run, template, redirect
  import dataset


  db = dataset.connect('sqlite:///database.sqlite')
  entries_table = db['entries']


  @get('/')
  def show_entries():
      entries = entries_table.all()
      entries_sorted = sorted(entries, reverse=True)
      return template('entries', entries=entries_sorted)


  @post('/add')
  def add_entry()
      entry = request.forms.get('entry')
      entries_table.insert(dict(
          text=entry,
          created_by=datatime.utcnow(),
      ))
      return redirect('/')


  run(reloader=True, debug=True)

- [0] https://bottlepy.org/docs/dev/

- [1] https://dataset.readthedocs.io/en/latest/

- [3] https://docs.pipenv.org/

Edit: formatting.

I get what adtac said, but, "not use node for cli tools?" Come on, so if I only know JavaScript and I want to build a cli tool for personal use that can later open source, shouldn't do it because the language?

That's not the hacker mentality, you can write a cli tool with JavaScript, Python, Lua, etc., make it work and there's nothing wrong with it. If you want to go full deep into cli tooling, then you start to looking into other languages that can fit into your new requirements.

JavaScript classes are syntactic sugar, the class type doesn't exist in ES2015; everything still works with prototypical inheritance.

So, I'd say that this book is still relevant Today. If you don't understand how inheritance work behind the scenes, you don't understand JavaScript.

I don't know why, but just by reading the title my mind implied JavaScript, and I noticed it doesn't have that word only after reading your comment.

Weird.

This.

> I don't know, I think some people feel a bit threatened by this move.

You are right, but as you said, is good to have alternatives.

> It could be viewed as a way to subvert the Linux and OSS community.

Good, is healthy to have competition.

More snarky than usual, i don't know why. "why not just" or "just use" kind of comments that you see more in reddit.

Even someone recommended an Electron alternative, on HN! the #1 Electron hater community.

Interesting.

This.

Accessibility is another benefit from using Bootstrap. From someone who "hated" bootstrap in the past, this feature is the most significant for me.

I'd like to know this as well

I started my self-taught career at 29, now 33, I've a full time job as front-end developer.

I switched from sales in the construction area in a different country. I came here with no English, no friends, no contacts.

So I think you can become a front-end developer.

It went like this:

* 29 to 30 freelancing

* 30 to 31 full time at a mid-size design agency

* 31 to Today full time at a big company

Ping me if you need help or advice (if I can provide any) at twitter @_jolvera or email jolvera at posteo.de

Edit: formatting

Python + Bottle + SQLite + Vue/Preact

Mostly small side projects.

there are two kinds of people, the ones that want to learn how to do it "manually" and the script kiddies.

wifite2[1] is a wrapper tool that does all this automatically.

Not trying to say that easier is better, in this case. Just wanted to show this tool for those who don't know it.

[1] - https://github.com/derv82/wifite2

edit: added wifite initially, replaced it with wifite2

Or GitHub's wiki

I see this argument everywhere, but, when the application is done properly, the reloading doesn't feel that bad.

Related past threads:

- Ask HN: Are there any solid arguments against SPAs in 2017? https://news.ycombinator.com/item?id=13315444

- Do you really want a single-page application framework? https://news.ycombinator.com/item?id=12956059

- The Disadvantages of Single Page Applications (2014) https://news.ycombinator.com/item?id=9879685

I've been a web developers for 5 years like the author, and, I as well, went through the jQuery, Knockout, Backbone, React, Vue road. On my daily job I use Node & React/Redux, on personal projects, I prototype in Python using bottle and vanilla JavaScript with axios[1].

Before, I wanted to use the latest stack, maybe looking for approval from the "community", something like: "Hey, I'm building a X app with Express, React, React Router, Redux, Immutable..." But by the time I had the basic setup, my motivation was gone (at that time there was no react-starter-app[2]).

So I'd say you should start with whatever you are most comfortable, doesn't matter if it's React or jQuery. The goal, IMO, is to start building stuff.

Now, I just don't care what's the latest JS framework, I don't dislike them, all the opposite, I get excited about them[3], but I focus on what's my best weapon for the job.

- [1] https://github.com/mzabriskie/axios

- [2] https://github.com/facebookincubator/create-react-app

- [3] https://github.com/KingPixil/moon

Some more:

- http://webaim.org/resources/contrastchecker/ (great tool)

- https://24ways.org/2012/colour-accessibility/

- https://www.viget.com/articles/color-contrast

As long as you understand idioms, programming paradigms in general, and good patterns in specific languages (e.g. list comprehension in python, prototypal inheritance in js, metatables in lua, etc.) you shouldn't be afraid of showing off your stuff in X language.

I know good Java developers that have become really good front-ends.

I know experienced developers that have few or none activity in GitHub at all. So, it depends.

You could find developers that:

1. write good code and are active in the community

2. write good code and are not active in the community

3. write ok code and are active in the community

4. write ok code and are not active in the community

5., 6., etc., (... you get the idea)

So, with number 2, you could see an empty GitHub profile and perceive it as low quality, but that's the wrong perception. See `pyrophane` comment as example.

Obviously on a hiring process a GitHub profile with activity is a great plus, but, again, it depends.

I wouldn't mind. But it doesn't work that way, look:

https://vimeo.com/58808364