Here’s the link, welcome!
1 Like
Wow, this was so great! I counted 25 people joining in total and we ended up staying in the call for 3h 
I would like to express my gratitude to every single one of you for making it such a joy! 
During the call we talked about making this happen again on a regular basis. Some of the open questions were:
- should we have talks sometimes?
- should we have a dedicated call to answer beginners questions?
- how often should this be? Is “every two weeks” a good timespan or should we commit to “once a month” instead?
Right now I think we agreed that:
- I personally don’t have the bandwidth to organize anything more complex than “let’s have a relaxed call and talk about anything really”, so if we’d like something more structured we’d probably need someone else to help with that (mostly to chase speakers around, moderate and schedule things).
I think we would be able to put together some small talks quite easily though, e.g. @kritzcreek offered to talk about building typesystems, and I could host some kind of workshop on the registry stuff and/or Dhall (or other things, feel free to ask).
Anyways if someone wants to talk about something please PM me or post here, and the same goes for helping with logistics
- we can try having this every two weeks for now, so I’m going to tentatively schedule the next happening on Monday 11th May at 20:00 CEST
However, I’m a little bit unsure about the time. E.g. this works ok for EU people since it’s in the evening, but might not be perfect for people on American timezones (since they might be in other work meetings) and it’s definitely not good for East Asia (since they should be sleeping at that time). So, I’m open to suggestions about times that might work better for audiences in other parts of the world. Please follow up here
Cheers! 
11 Likes
One proposal that was brought-up during our breakout room session is organizing working groups around some of the themes we discussed, such as:
- Tooling
- Ecosystem
- etc.
It would be nice to review what everyone is working on in a particular area, and brainstorm ideas of what to do next. With some recorded meeting notes, we could even come out of these sessions with some sort of roadmap. I’d like to discuss plans for improving new-user experience in a breakout room during our next meeting.
Q&A for beginners with voice and screen-share would also be great to offer. When starting out, I could have really used some pair-programming-style assistance for clarifying topics that were difficult to even figure-out how to write-up for Slack. This is my favorite feature of in-person programming meetups, and it would be wonderful if we could reproduce this online.
4 Likes
The breakout room feature seems like a genuine gamechanger for this kind of meetup, with the possibility to be really transformative. In particular, it seems to me to offer the possibility to make online event much more like an “unconference”, as Fabrizio was talking about at the beginning, that addresses several distinct community needs and yet is not diffuse and hard to follow. It also allows a lot more people to speak and ask questions.
I think yesterday’s format could actually be a good template with the addition of 1 short prepared presentation at the beginning. Like maybe a presentation that’s interesting to all but accessible to beginners, followed by breakouts that cover at least the three most common-but-sort-of-mutually-exclusive things that communities need:
-
answering beginner’s questions
-
discussing futures, technical ideas, papers
-
open chat that just fosters some community
It’s been my experience with online communities going back to the 1980’s and USENET that many virtual spaces gravitate to serving only one of these needs, to their eventual detriment. And if instead they have separate forums the time commitment becomes too much for the biggest contributors.
At any rate, i’m definitely willing to participate in a fortnightly or monthly call and to do my share of answering beginner’s questions and questions about my experiences in bringing FP/Purescript into a team and the challenges and successes of that.
Many, many thanks to @f-f Fabrizio for organizing and for all who participated.
4 Likes
However, I’m a little bit unsure about the time. E.g. this works ok for EU people since it’s in the evening, but might not be perfect for people on American timezones (since they might be in other work meetings) and it’s definitely not good for East Asia (since they should be sleeping at that time). So, I’m open to suggestions about times that might work better for audiences in other parts of the world. Please follow up here
I think it’s better that there’s at least some activity in the community doing an Unconference-like thing rather than one that tries to work for everyone and fails to accommodate everyone. If this time works best for EU, why not let that be? While I don’t want to segregate people based on time zones, I also realize that it takes someone to organize these things. Why not use this as a testing situation to create a model that people from other timezones can follow? That being said, I would appreciate it if those presentations could be recorded so that those of us who can’t be there can still watch it later.
4 Likes
Thanks to @f-f for organizing and @kayla for providing the Zoom! It was really nice meeting everyone and hearing about their various backgrounds and experiences. Looking forward to the next one!
6 Likes
I thought it was a cracking good meetup. Thanks to @f-f for organizing.
There is no good answer to the time of day issue, so we may as well stick with 20:00 CEST.
I tried to move rooms on the call but that is not generally allowed – the host has to assign people and, once assigned, people can not move themselves. There is a workaround to this, which is to make everyone a co-host (see https://medium.com/swlh/how-to-run-a-zoom-cocktail-party-and-have-better-classes-conferences-and-meetings-too-dc2c5b58f8be). That requires a some trust in the participants not to abuse the additional powers, but is something to think about.
We might also publicly note at the beginning of the call that we are “lurker friendly”. If people want to just watch and listen that is fine. Some gentle encouragement to turn on your camera even if you’re lurking would be nice, but of course nobody is compelled to do anything.
6 Likes
I’ve talked to Fabrizio and we agreed that it would be good to see if we can can adjust the next meetup timing so more of the interested PureScripters could join.
So please check all the hours when you would be able and would like to join the next meetup (on Monday 11th May):
- 12:00 UTC
- 13:00 UTC
- 14:00 UTC
- 15:00 UTC
- 16:00 UTC
- 17:00 UTC
- 18:00 UTC
- 19:00 UTC
- 20:00 UTC
- 21:00 UTC
0 voters
3 Likes
How long is the meetup expected to last? My selections depend largely on the duration.
Last time we clocked around 3h, but:
- I’d say it’s really fine to join and leave at any time
- This time I’d try to run it shorter, e.g. max 2h
3 Likes
So it looks like 21 UTC is the most popular time but that’s a bit late for me, so tomorrow we’re going to start at 20:00 UTC - feel free to join anytime (I predict we’ll stay on for a couple of hours at least).
I’ll post the link here shortly before.
4 Likes
Meeting link - I’ll start adding people in 15 minutes, so expect to queue for a bit if you join already now
Thanks everyone for the lovely meetup, I thoroughly enjoyed chatting with all of you and I hope you had a great time too!
Keeping up with our two-weeks schedule I’m going to fix our next meeting for Monday 25th of May, but this time it will be at 13:00 UTC, so that it’s earlier for us in Europe, still includes US East Coast, and allows peeps from Japan and East Asia to join too
6 Likes
Wanted to capture this discussion point from today’s meetup, since this question comes up occasionally:
What’s missing from having PureScript 1.0?
- Package registry
- ES6 modules
- Better dead code elimination
- Recommended bundling workflow
- Solid documentation
- Smooth new-user experience
The focus is to make sure that things are working really well before opening the floodgates to all the new users that will accompany a 1.0 announcement, rather than merely meeting the semantic versioning requirement of no upcoming breaking changes in the language.
Also, esbuild was mentioned as a candidate for recommended bundler once the ES modules feature is complete.
4 Likes
Just some thoughts on how to make this time better for everyone
Before the meeting begins, I think it would be good to let others know what is one thing each person attending wants to get out of a given meetup. This will help us know how many breakout rooms to make as well as who will be in those groups.
4 Likes
Yeah that’s great feedback, thanks. The last time we all had a couple of minutes to introduce ourselves so that it was quite smooth to figure out what to do, but this time it was a bit more chaotic - probably due to being super late for me - and I apologize for this.
Next time let’s have a quick round of “I’m here because…”, so that we can spend our time more efficiently 
2 Likes
Oh, I was thinking we would post an opening thread on Discourse “There will be a meetup on Day X at Time Y. If you plan on coming, post 1 thing that you want to get out of this meetup. For example, what’s something you want to learn? or discuss? or work on together?” Then people would post all of that in the thread. Then someone could organize this information into the following:
- number of people coming
- recommended breakout rooms and who will likely be in each
- miscellaneous instructions for people before it starts (like “you have to be assigned to a breakout room before the menu option that allows you to switch between them will appear on your interface”)
That way, we reduce the amount of time making intros because people are already familiar with what others are doing / want to talk about / their background.
7 Likes
So I made a small fork of the halogen template which uses esbuild instead of webpack!
Feedback would be appreciated!
2 Likes
Thanks for investigating and making this easy to reproduce. I like your strategy for eliminating duplicate index.html files. I’ll have to incorporate that into this template. pnpm may also be a better recommendation for new users (more discussion about that here).
Is there a way to enable automatic page refresh on file save with your workflow? That’s how the other template repo is configured.
Bundle size probably isn’t the main selling point of esbuild, but for reference, it produces a 129 KB bundle (29 KB gzip), which is around what we get with parcel (126 / 27 KB).
2 Likes
