Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Is there an insight on why?

Is it because VC were willing to give less to them because they were women? That there were less well connected? That their negotiation skills didn't match up? That the nature of the projects they choose were perceived as less attractive?

Lots of possible reasons here, and the solutions to choose can be very different depending of the causes.


as always, there's xkcd: https://xkcd.com/552/


Can you say more about that?

I though SQLAlchemy core goal was exactly that. When does it fails, compared to Csql?


My desire was to be able write real SQL directly in the dialect of my database.

SQLAlchemy can't give me that, instead I'd need to learn a special SQLAlchemy-specific query builder syntax that probably won't support all the analytical functions I want to use anyway. It's really a whole different beast to csql.


From what I understand, not only SQLA API does provide support for all functions you wish to use, but it provides also raw SQL escape hatch.

What kind of limitations did you encounter in the past?


After ".py", use " ?" (the space is important) to force the search in firefox.


Using a question make in front of the term is traditionally how some browsers trigger search. They usually have a jeybconbe to add it automatically.

For example, in firefox and chrome ctrl-l will clear the URL bar and put the cursor and focus there to take you to the location you enter, and ctrl-k will do similar but pre-fill the location bar with a preceding '?' so a search is triggered on the input.

These shortcuts have existed for quite a while. They used to just focus the respective separate input boxes, when it wasn't all done through one.


What's a "jeybconbe"? It's a googlewhack for this thread.


And six hours later, as I read this thread, nobody has registered the domain still! ;-)


My best guess is that it looks like a typo for "keycombo".


Yes, thanks. Switched to a new keyboard on my phone, and I'm getting some different typos now. Not necessarily more, I always seem to have a lot that slip through, just different...


Or just start the query with `?`

Typing `?bla.py` in the omnibar will perform a search for `bla.py` on both Firefox and Chrome


I maintain several open source projects. Sometimes PR are not merged for years.

I'm not payed for this, I'm not even thanked for this most of the time, so I'm certainly not going to set any deadline.

But forking might be a solution, if you can give the necessary horse power for the long run.

Most can't.


It’s odd to me how nontechnical people have migrated to GitHub to make bug reports on software they use.

The other day, I was trying to use a Python library to scrape some stuff. It kept breaking. I looked on the issues page and there were many, essentially useless bug reports asking them to fix the issue. I opened up the script and changed about 7 lines and it worked fine.


There are two factors at play here I think. The first is that Github has become quite popular. The second is that Github has worked a lot on usability - it's now very easy for users who are not very technical to create an account and report issues.

At times I imagine there could be some kind of "I know how to report bugs"-certification that people could somehow earn. Projects could then use this as a barrier to prevent getting too many useless issue reports.

The problem really goes both ways - as a software dev I'm disincentivized to report detailed bugs to projects, because there's a high risk it will get drowned out in the noise.

Some projects have quite specific templates for reporting issues. This helps a bit, but you still need someone to go in and remove issues that don't match the template, and few people want to volunteer for that work.


Yeah, I guess it’s just an entirely different kind of engagement.

I mostly use GitHub to find off the shelf solutions to whatever problem I’m having or to avoid doing the work myself. If I run into any problems I have with something from there, I either try and fix it by tweaking the repository, using another, or just building the thing myself. I think the last time I reported an issue on an external repository was because of something I was made to use at work.


Well, they look for a channel to communicate their frustration. Most are closed. This one is open. The water follows the path of least resistance.


I've noticed this trend too -- but I've also noticed people starting GitHub Repos for websites/apps just for the Issues.

No code, no PRs, just a way for the public to create Issues.

Not sure what this means for the "culture of code" other than things are blurring...


At least there is a feature called 'discussions' coming soon to github. That should hopefully minimize the abuse of issues. But that is also due to the fact of current github. Not everyone is displaying their email and there is no other communication channel.


I think a lot of it is maybe bleed over from gaming communities, especially emulators, maybe rom hacks too? I’ve noticed barrages of useless bug reports on those repositories. But I’ve been surprised to find them on far afield stuff as well.


People keep confusing program configuration files and program stdin and are surprised that TOML is not a good fit for it.

If you are provisioning servers from a TOML files, you're doing it wrong. That's your program main input, not config.

If you have deeply nested values, chances are you are again confusing configuration vs main input.

JSON and CSV are great main input formats.

TOML is a great configuration format.

YAML and XML try to do both, and end up doing average on either, but being abused for all of them (looking at you Ansible and Solr).

So you should use each format for the correct purpose, as usual.

A config file looks like ~/.ssh/config or /etc/nginx/nginx.conf, not like ~/.ssh/authorized_keys or /etc/nginx/site-available/default.conf.

Just because we love to put a lot of data input in config folders (.config and /etc are full of input data) and call that configuration doesn't make it so.

How to know if something is configuration and something is input?

Conf data is usually only manually edited (authorized_keys changes with the life cycle of the program) and doesn't contain logic (default.conf if full of logic). Conf is also how the program is going to behave when performing its main task, the boostraping state, not the data used for it's main task (so not ip for provisioning servers, which is not meta, but the main course, or default.conf, which nginx uses to perform the main task). Conf rarely changes, main input often does. Conf is not piped or redirected to stdin.


That's not config data that you have here, that's your program input (hint: you pipe it to stdin).

TOML is for config, config that users edit by hand, not input.


That looks like hand-edited config to me. At least, I've maintained files similar to that in past gigs. It's a nice example of how CSV can work well if you don't need to worry about quoting.


1 - you don't pipe config to stdin. If you use standard input, that's your main input.

2 - config sets your program boostrapping state. It's not the main data your program processes. That's your main input. IP addresses are what the script processes. It's not config.


1 - If you google 'config stdin' you'll see a number of good reasons a program might want to accept configuration on stdin. (also, not that it matters, but my program read it from a file)

2 - Those IP addresses are probably not the main data the program processes. In my case, they were configuration, describing where an auditing processor scrapes input and how to allocate compute.


Scraping is not bootstrapping. That's the main process. Main input can have several sources.


If you're redefining the main input to include all input data (including hand-edited CSV files) then you're just contradicting yourself. This conversation is tedious and unproductive, I'll leave you alone.


Config is data. Data is input.


Anything that is not hardcoded is technically input.

But there is a reason we have a word for config.

It's a specific kind of input: it feeds the boostrapping state of your program, it's not the main data your program process.

The difference is important: structure, complexity and dynamism requirements are not the same.


I had to create a deb for a web app, it had to setup and populate a DB (from web sources), and manage updates for this db when you upgraded the deb. It had a build process of static files that couldn't be vendored. It has a lot of configuration to be entered prior those would happen, using debconf. It had to vendor a virtualenv. I had dependancies on 2 other web apps that had the same story, and they shared some config files.

I didn't chose this architecture. But I was tasked to package it so that people could just "apt get install stuff" and start using it.

It was HARD.

The tech is very old school, it doesn't give a lot of feedback, it's hard to debug, documentation is sparse and examples in the wild are not up to date, not to mention the state of tooling. And you do all that with shell scripting, the worst language for the job. Sure you can use anything else, if you like zero doc and example.

Then we had to distribute it.

Well, turns out creating an APT repo is not so easy, either.

Now, we did all that by cutting a lot of corners, zero red tape, and only us to please. Also, the consequences of not using best practices, or worst, breaking something, were few.

On a team of 6, only 2 were really understanding what was going on. The rest were lost, awaiting instructions from us because they just couldn't picture were their work would fit in this blob of bash workflow. Now that I'm gone, I have no idea how the team is going to maintain the thing.

I can't imagine doing the same thing with the level of road block working for something as sensitive as the official debian repo would bring.

If debian wants more contributors, they have to make this stuff way, way more accessible. And be friendlier with people telling them it's hard.

Every time I raised the topic, somebody came along to say I shouldn't be doing x or y. Or just that I shouldn't be packaging something and just publish it on the debian repo, letting the debian maintainers do the packaging. It's not going to bring me to work with the community if the first taste of it is the demonstration they completely ignore their shortcomings.

And I say that while I've been typing apt commands for a decade now. I'm also french. Debian is, with VLC, Libre Office and Firefox, one of the 4 pillars of FOSS for me.


Making deb _is_ painful, the politics of how packages are folded, bent, welded, drilled and smashed is not a simple landscape to navigate.

A lot of Docker is a response to how difficult it is to build packages and how invasive package installation is to the base system (Nix gets this right).

If in the future you need to build packages again, I'd take a look at fpm.

The goal of fpm is to make it easy and quick to build packages such as rpms, debs, OSX packages, etc.

https://fpm.readthedocs.io/en/latest/

https://github.com/jordansissel/fpm


In production systems, you don't use coroutines alone. You have several processes, some may contain several threads, some thread may contain an event loop.

In fact, it's already the case with WSGI setups: you may have async nginx on front, multi-process gunicorn behind, and a thread pool for you db connections. And asyncio already provides API for sending tasks to process pools and threads and getting them back as async Future as a convenience. It's turtles all the way down.

Bottom line, async, threads or processes are not silver bullets, and you should use the right tool for the right job.

Just like when Go users realized that spawning goroutines for everything actually didn't work at scale, throwing awaits everywhere is not a magical solution.

Having asyncio at your disposal make some tasks easier, like websockets, crawling your network, etc. It opened the door for new architectures, and maybe new features (live settings, task queues that feeds the results back to you, etc.).

But it's been oversold, as with anything new and shiny.


Async is perfect for things like bulk uploading to DynamoDb while you munge through input files or save metadata to postgres.

But for 97% of the use cases it's easier to use multiple processes and a normal worker queue.


Genuine question, what good does the ability to buy and sell stock on the short term do for humanity ? Does it have any specific vertue appart from allowing one to make make money by betting correctly ? Why are not all sales required to be long term ?


Every buy is a sale, and every sale is a buy.

I am a long term investor. Long term investors like me still need to buy or sell stock occasionally, even if only to live out their retirement eventually.

There's no good reason to assume that for every long term who wants to buy or sell on a particular date, there will be another long term investor on the other side of the deal.

So a special kind of short term investor, called a market maker, jumps in. Market makers typically hold a small amount of inventory and offer to buy or sell stock.

Market makers allow your grandma to sell stock any day of the week without worrying too much about timing.

See https://en.wikipedia.org/wiki/Market_maker

There are other kinds of short term holders of shares. But market makers are probably the most obviously useful to long term investors.


The fact that stocks can be bought and sold quickly has a use, namely that the price should signal how the market values this asset.


But what good does it do to have such a instant information on speculative value outside of the world of making money with it ?


I think we can both agree that there is a lot of value in knowing the "actual value" (as opposed to speculative value) of things in our society. Knowing the actual value of things is impossible for multiple reasons it (it changes very fast and is just intrinsically very hard). However, given a big incentive (making money) we can let the market estimate the value of goods for our society. This speculative valuation is far from perfect, but it is the closest we can get to the actual valiation of goods/institutions.


It prevents capital being mis-allocated.

It turns out that is one of the most important things to do in modern, capital intensive, economies.

It also means people can invest for shorter periods and that means more capital is available for investment. This has a double bonus where it reduces the risk of investments again making more capital available...


I don't have the background to understand your answer, can you make it simpler with some examples ?


No worries, it's all quite counterintuitive :)

Imagine if you're a would be investor. You're money is available now to invest. So you want the market to be open to let you buy. Otherwise that cash is just sat there waiting. Similarly, you want to invest all your money. But if you know you won't be able to get it back for X period of time then you can't can you? You might not even know how long you can invest for: I might reasonable expect not to need some cash till Christmas time but if I lose my job tomorrow I want it now please!

So a market where you can buy and sell rapidly makes you more able and more likely to invest. That's good for you as you can use spare cash productively and make a profit while still being safe if you suddenly have a change in circumstances. It's also it's good for the company you're investing in as they can raise capital quickly and there is more capital available. And all of this means more growth and lower costs and that means more tax money for social services and more jobs for other workers etc.

The analysis for the people receiving the investment is similar but a bit more complex because the company doesn't just get investment, it also get's information: a rising share price tells you you should expand, high prices in general indicate a great time to start new businesses, a competitor whose share price falls while your one rises has issues and might be open to a merger\takeover etc.


It seems just to soak away capital to third parties and not prevent misallocation any more than longer-term trading would?

Compare football (ie soccer) trading windows. Player performance within a match might be like daily performance of a company.


Not a strong conviction from me but I can see a case for liquidity when you can sell quickly.


I'm not talking about the times it take for selling as much as the absence of delay between buying and selling.



Factors, the world, the firm trading, etc all change daily. Also market makers provide liquidity through buying and selling quickly.

If you had to hold a stock for a long amount of time before selling it, you would find it very hard to buy or sell stock.


If there was no short term market then long term buyers and sellers would have a harder time buying and selling and it would cost them significantly more.


Same, but I also do "shopt -s dotglob" so that * includes hidden files.


That's really fun to pronounce.


ooh good one, I'll add that to my snippet


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: