Hey all, I just created https://proposals.es which, like the title says, lets you browse through ECMAScript proposals.
Some of the main features:
* All proposals are colocated in one place and sorted by stars (In the tc39/proposals GitHub repo it is split up in 6 different markdown files with proposals in no particular order)
* You can filter proposals via search
* Proposal READMEs as well as additional details show side by side
* Proposals without a README still render as an iframe
Likewise for me, I would love if I could reach out to you. I had applied awhile back and hadn't gotten a response, and did not have any way I could mention that I saw the post here. Would be greatly appreciated, thanks.
Thanks for the suggestions! I'll try to improve the contrast. As you mentioned, most of the templates I chose were the popular ones from sites like ShareLaTeX and Overleaf. I am happy ot add more templates, if someone were to open a "Template Request" issue on the repo.
And yeah, I was hoping to add import/export to json as well as an "import from LinkedIn" functionality.
Thanks! I was definitely planning on adding an import/export feature so that you don't have to keep starting from scratch, so I can try to see if I can make it compatible with jsonresume too.
Hey all! latexresu.me is a website for generating LaTeX resumes easily.
Basically, you just choose a template, fill in as much (or as little) info as you want, and click "Preview Resume" at any point to see your current generated PDF. You can switch your template on the fly at any point and once you're happy with your results you can download the PDF or the generated LaTeX source code. Please let me know what you guys think!
Is there a more Pythonic way to do it? Lambdas are cool but usually not the first place you go in Python. I would think something like (my best guess, not a Python pro)...
sum_of_squares = sum([x*x for x in arr])
Which I think is easier to read than either example post above.
Of course you will point out that this is less powerful than full map and reduce.. but meh... pros and cons to both styles
Worth noting that map() can be parallelized whereas a list comprehension can't necessarily (since it is an explicit loop). The multiprocessing module allows trivial map parallelization, but can't work on list comprehensions.
So I have coded everything from dumb web servers (tm), to high performance trading engines (tm). I have toyed with doing the list in parallel thing... and used it in a toy GUI tool or two I wrote... but never really found it that useful in the real world. If you actually want high performance, doing a parallel map is not going to be fast enough. If you are a dumb web server, it's a waste of overhead 99% of the time.
But hey, if you want to use map when you actually need to do a parallel map, cool. But seems very very uncommon. ~ 1 in 10,000 maps I write.
That example works only because the function sum is already defined in Python. If you wanted to do something less common than summing up elements you would have to either use reduce or implement a for loop.
In Python 3, reduce was intentionally moved into the functools library because it was argued that its two biggest use cases by far were sum and product, which were both added as builtins. In my experience, this has very much been the case. Reduce is still there if you need it, and isn't any more verbose. The only thing that is a little bit more gross about this example is the lambda syntax; I would argue that even that is a moot point, however, since Python supports first-class functions, so you can always just write your complicated reduce function out and then plug it in.
I just counted the number of reduce I used in my current python project (6k lines). reduce comes up 32 times. And by comparison, map is used 159 times and filter 125 times - for some reason I tend to use list comprehensions less than I should.
That seems like an argument against lambda functions in general - why use lambdas when you can define a static function for every case? Well, the answer in my opinion is because it makes code more readable if you can define a simple lambda function instead of having to name every single function in the code base.
What's the advantage of list comprehension over lambdas (assuming the lambda syntax is decently lightweight)?
I feel like I come down hard on the side of lambdas, but I've never really spent enough time in a language with list comprehension, so there's a good chance I'm missing something.
how can you come down hard on the side of one when you've never experienced the other?
I'm from a non-list-comprehension background too, but recently started working a lot in a large python codebase, and have found the dict/list comprehensions to be beautiful. I'm a huge fan. It's a shame lambda syntax is not the best and it's generally crippled, but comprehensions are a great 80/20 compromise for handling most cases very cleanly.
I find it a lot easier to read, part of which is that I'm used to the Scala way of sequence dot map function. When I see the python one I can't remember if the function comes first or the array.
I'm not positive, but I think it saves the need to create a new execution frame for each lambda call, since the whole loop executes in single frame used by the comprehension.
In theory I suppose the VM could have a map() implementation which opportunistically extracts the code from a lambda and inlines them when possible; but doubt CPython does that. OTOH, I'd be surprised if PyPy doesn't do something like that.
I'm not meaning when the comprehension is invoked, but during each iteration of the loop within the comprehension.
When doing something like `map(lambda x: 2+x, range(100))`, there will be 101 frames created: the outer frame, and 100 for each invocation of the lambda.
Whereas `[2+x for x in range(100)]` will only create 2: one for the outer frame, and one for the comprehension.
Some of the main features:
* All proposals are colocated in one place and sorted by stars (In the tc39/proposals GitHub repo it is split up in 6 different markdown files with proposals in no particular order) * You can filter proposals via search * Proposal READMEs as well as additional details show side by side * Proposals without a README still render as an iframe
You can find the source on GitHub: https://github.com/saadq/proposals.es. Built with Next.js, React, and TypeScript.